home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
o22516d1.zip
/
IBMPTF29.DOC
< prev
next >
Wrap
Text File
|
1994-01-05
|
229KB
|
4,653 lines
i
README.TXT FOR
CICS OS/2 1.2.0 SERVICE LEVEL 29
28 October 1993
TABLE OF CONTENTS
─────────────────
Introduction . . . . . . . . . . . . . . . . . . . . . 1
Current Level . . . . . . . . . . . . . . . . . . . . . 1
Hints and other information. . . . . . . . . . . . . . 1
Changes due to fix for APAR PN38509 . . . . . . . . . . 2
1
INTRODUCTION
────────────
CURRENT LEVEL
─────────────
The current level of CICS OS/2 is 1.2.0. Service Level 29.
HINTS AND OTHER INFORMATION.
────────────────────────────
Required PTF levels for OS/2 Versions
─────────────────────────────────────
┌─────────────┬──────────┬──────────┬───────────┬───────────┐
│ │ OS/2 1.3 │ OS/2 2.0 │ OS/2 2.0+ │ OS/2 2.1 │
│ │ │ │ XR06055 │ │
├─────────────┼──────────┼──────────┼───────────┼───────────┤
│ CICS OS/2 │ │ │ │ │
│ PTF Level │ 4 │ 16 │ 23 │ 23 │
│ │ │ │ │ │
└─────────────┴──────────┴──────────┴───────────┴───────────┘
Required Import Groups
──────────────────────
The following is a table which indicates the import groups introduced at
each PTF level. Systems being upgraded from a previous PTF level may require
to import screen file changes. For example a customer upgrading from PTF
level 18 to the current level would require to import groups PN21505,
PN28420 and PN29610.
┌─────────────┬────────────────────────────────────────────────────────────┐
│ PTF level │ Import Group(s) │
├─────────────┼────────────────────────────────────────────────────────────┤
│ 1 │ PL61234, PL61239 │
├─────────────┼────────────────────────────────────────────────────────────┤
│ 8 │ PL71166, PL81305 │
├─────────────┼────────────────────────────────────────────────────────────┤
│ 17 │ PN15480 │
├─────────────┼────────────────────────────────────────────────────────────┤
│ 19 │ PN21505, PN28420 │
├─────────────┼────────────────────────────────────────────────────────────┤
│ 21 │ PN29610 │
└─────────────┴────────────────────────────────────────────────────────────┘
2
Changes due to fix for APAR PN38509
───────────────────────────────────
Apar PN38509 has added the following CICS OS/2 error message.
FAA1336 HELP FOR MESSAGE FAA1336W
Text: FCT Max Record Length for FAAMSFSC is too small.
Explanation: The Max Record Length value in the FCT definition for
FAAMSFSC is too small for the size of map being
imported/exported.
System Action: The map will not be imported/exported.
User Response: Increase the Max Record Length value in the FCT definition
for FAAMSFSC. The recommended value is 23084.
**************************************************************
**************************************************************
*** ***
*** End of PTF 29 updates. ***
*** Updates for previous PTFs follow. ***
*** ***
**************************************************************
**************************************************************
i
README.TXT FOR
CICS OS/2 1.2.0 SERVICE LEVEL 28
30 July 1993
TABLE OF CONTENTS
─────────────────
Introduction . . . . . . . . . . . . . . . . . . . . . 1
Current Level . . . . . . . . . . . . . . . . . . . . . 1
Changes due to fix for APAR PN38181 . . . . . . . . . . 2
1
INTRODUCTION
────────────
CURRENT LEVEL
─────────────
The current level of CICS OS/2 is 1.2.0. Service Level 28.
2
Changes due to fix for APAR PN38181
───────────────────────────────────
Apar PN38181 has added the following CICS OS/2 error message.
FAA1897
Text: Field is defined outside of the SIZE operand parameters
Explanation: The combined LENGTH and POS of the given field
would cause it to spill over the end of the map.
The map size has been defined on the DFHMDI
macro at the beginning of the map.
**************************************************************
**************************************************************
*** ***
*** End of PTF 28 updates. ***
*** Updates for previous PTFs follow. ***
*** ***
**************************************************************
**************************************************************
i
README.TXT FOR
CICS OS/2 1.2.0 SERVICE LEVEL 27
19 May 1993
TABLE OF CONTENTS
─────────────────
Introduction . . . . . . . . . . . . . . . . . . . . . 1
Current Level . . . . . . . . . . . . . . . . . . . . . 1
Changes due to fix for APAR PN30850 . . . . . . . . . . 2
1
INTRODUCTION
────────────
CURRENT LEVEL
─────────────
The current level of CICS OS/2 is 1.2.0. Service Level 27.
2
Changes due to fix for APAR PN30850
───────────────────────────────────
This APAR was created to allow further error diagnosis for resource
shortage problems when using the CICS OS/2 ETI feature. A number of
new tracepoints have been included. A full list of these ETI
tracepoints follows.
┌─────────┬──────────────────────┬───────────────────────────────────┐
│ ID = 55 │ Issued by FAAOMPML │ OS/2 Main Control Task │
├─────────┼──────────────────────┼─────────────────┬─────────────────┤
│ TYPE / │ ENTRY DESCRIPTION │ FIELD A │ FIELD B │
│ POINT │ │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SO H01 │No free entries in the│ 'NO3E' │ 'NTRY' │
│ │external request table│ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SO H02 │Error opening FAACTFTB│ RC │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SO H03 │Error reading FAACTFTB│ RC │ │
│ │Starting │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SO H04 │Error in DosAllocSeg │ RC │ │
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
**************************************************************
**************************************************************
*** ***
*** End of PTF 27 updates. ***
*** Updates for previous PTFs follow. ***
*** ***
**************************************************************
**************************************************************
i
README.TXT FOR
CICS OS/2 1.2.0 SERVICE LEVEL 26
16 April 1993
TABLE OF CONTENTS
─────────────────
Introduction . . . . . . . . . . . . . . . . . . . . . 1
Current Level . . . . . . . . . . . . . . . . . . . . . 1
1
INTRODUCTION
────────────
CURRENT LEVEL
─────────────
The current level of CICS OS/2 is 1.2.0. Service Level 26.
**************************************************************
**************************************************************
*** ***
*** End of PTF 26 updates. ***
*** Updates for previous PTFs follow. ***
*** ***
**************************************************************
**************************************************************
i
README.TXT FOR
CICS OS/2 1.2.0 SERVICE LEVEL 25
16 March 1993
TABLE OF CONTENTS
─────────────────
Introduction . . . . . . . . . . . . . . . . . . . . . 1
Current Level . . . . . . . . . . . . . . . . . . . . . 1
Implementation of C-SET/2 Support . . . . . . . . . . . 2
1
INTRODUCTION
────────────
CURRENT LEVEL
─────────────
The current level of CICS OS/2 is 1.2.0. Service Level 25.
2
Implementation of C SET/2 Support.
──────────────────────────────────
This PTF adds support for the 32 bit C Compiler IBM C SET/2 and the debugging
aid IPMD. The following text describes the additional features available
after the installation of this PTF.
New features in this release
────────────────────────────
1) 32-bit support for OS/2 Version 2
Other required products:
IBM OS/2 V2.0; GA level or later
IBM C Set/2 V1.0 32-bit C compiler; GA level or later - CSD 22 or later
preferred
Knowledge of how to build conventional 16-bit C programs for CICS OS/2,
and knowlege of how to build standard OS/2 .EXE and .DLL files using the
IBM C Set/2 compiler is assumed.
This update allows 32-bit C programs to be written to run under CICS OS/2
as CICS transaction programs. It also allows 32-bit ECI programs. There
is no support for 32-bit C user exits, nor for 32-bit programs making ETI
calls, nor for 32-bit programs making off-line system management
(import/export/field setting) calls.
The actual base CICS is unchanged - therefore all memory passed to or from
CICS OS/2 must not span a 64KByte boundary, so that pointers to the memory
can be converted between being either flat (0:32) for the 32-bit code,
or segmented (16:16) for the internals of CICS OS/2. Memory which can be
referenced using either a 0:32 or a 16:16 address is known as 'tiled
memory'. Ensure data objects are tiled by compiling with the '/Gt' option
or by using of the '#pragma seg16' directive. All memory returned from
CICS, e.g. with GETMAIN, or CICS commands with the SET option, or
COMMAREA, will be aligned so as not to span a 64KByte boundary. Data
objects on the stack (automatic storage) will not span a 64K boundary as
the stack is provided by CICS OS/2.
No memory object bigger than 64KByte may be passed to, or allocated by
CICS OS/2, as the base CICS OS/2 system is still only 16-bit.
32-bit C CICS OS/2 programs do not have to deal with segmented (16:16)
pointers - all CICS conversions are done automatically by a 'thunk' layer.
This conversion is done automatically for pointers passed to CICS OS/2,
and for pointers returned by CICS OS/2 with the EXEC CICS commands with
the SET option and EXEC CICS ADDRESS commands. The thunk layer is a
library module in FAACLIB.LIB which is linked into the application program
when an application program DLL is built.
E.g. EXEC CICS READ FILE(file1) SET(p) LENGTH(len) RIDFLD(rid1);
file1 is a flat (0:32) pointer to the file name
rid1 is a flat (0:32) pointer to the RIDFLD
p is returned as a flat (0:32) pointer to the file data
The one exception is pointers passed in user-defined areas, such as
COMMAREAs, storage obtained with GETMAIN SHARED, or the CWA. CICS OS/2
has no knowledge of data in these areas and makes no conversions. If the
3
pointers in these areas need to be used by both 16-bit and 32-bit program
then on the 32-bit side they should be declared using the '_Seg16'
qualifer.
C integers (variables declared with 'int') and enumerations ('enum') are
different sizes in 16-bit and 32-bit code, so care should be taken passing
these between 16-bit and 32-bit code.
Character variables default to being signed with IBM C/2 16-bit code and
unsigned with IBM C Set/2 32-bit code.
OS/2 functions are different between OS/2 V1.3 and OS/2 V2.0. Code using
OS/2 V1.X calls will need to be converted to use the OS/2 V2.0 calls when
the code is recompiled with IBM C Set/2, or it may be possible for the
user to supply the function declarations for OS/2 V1.X calls with
appropriate '_Far16 _Pascal' and '_Seg16' qualifiers manually.
Structure packing is another area where care needs to be taken.
Structures aligned on 1 byte boundaries may take up less storage, but
accesses to elements which are unaligned may be slower. Structure packing
can be controlled with a compiler option ('/Zp?', for 16-bit C; '/Sp?'
for 32-bit C), or the directive '#pragma pack(?)' or the qualifier
'_Packed'. In these examples '?' should be replaced by '1', '2' or '4'.
CICS OS/2 structures (e.g. EIB, ECI interface blocks, structures produced
by the map translator) are expected by CICS OS/2 to be packed on 1 byte
boundaries. With 16-bit programs this is achieved by compiling with the
'/Zp' option, which is a default for the supplied command files for
program compilation (CICSCTCL & CICSCCMP). The corresponding option for
IBM C Set/2 would be '/Sp1', but this is not now necessary and is not
automatically used by the command files for program compilation (CICS32TC
& CICS32CL), as the CICS OS/2 headers now include directives to achieve
this packing. The map translator also now generates these directives
automatically for the header files it produces.
The alignment of CICS OS/2 supplied structures (e.g. EIB, maps) can not
be varied, but with care, by using the '#pragma pack(?)' directive, or the
'/Sp?' option the storage alignment can be controlled for user structures.
This may be useful if different structure packing from the default is
required for other parts of a program. Existing 16-bit programs probably
use structures aligned on 1 byte boundaries, so care would be needed if
data in the structure was also referenced in a 32-bit program, as this
would have a default alignment of 4, and would not work.
Compiler options can be supplied using the enviroment variables ICC and
CICSICC. ICC provides the default options for all invocations of the IBM
C Set/2 compiler, even when compiling programs which have nothing to do
with CICS OS/2. CICSICC is used for options specifically for CICS OS/2 C
programs, and can override options given in the ICC environment variable.
An installation may wish to decide on standard compilation options.
Some recommended compiler options are as follows:
SET CICSICC=/W3 /Kf+i-t-x- /Sa
/W3 Maximum warning level
/Kf+i-t-x- all warnings except some which may be confusing
/Sa ANSI Standard for C
4
It is recommended that 16-bit and 32-bit modules are not statically linked
together into the same DLL.
When a 32-bit CICS OS/2 program is running the IBM C Set/2 compiler
library handles exceptions such as page faults and segmentation faults.
This means that an OS/2 trap screen does not appear, because the IBM C
Set/2 compiler library writes out diagnostic information to file handle 2
before ending the process. If the program is running on a full screen
terminal, then this will appear on the screen. If it is on a PM terminal
then output from file handle 2 is normally lost. By redirecting file
handle 2 on CICS OS/2 start-up, e.g. with: CICSRUN 2>>traps.log this
information will be appended to a file and will not be lost.
ECI programs may now be written using IBM C Set/2. The header file
FAAECIH.H has been changed to allow the existing 16-bit ECI to be called
from an IBM C Set/2 program. The ECI parameter block and commarea must be
allocated from tiled memory - i.e. memory which does not span a 64KB
linear address boundary and the address of which can be expressed as
either a flat 0:32 address or a segmented 16:16 address. This is achieved
by compiling with the '/Gt' option or by using the '#pragma seg16'
directive. The modified ECI header ensures the address of the commarea
will be converted to a segmented address when it is set up in the
parameter block and that the passed address of the ECI parameter block is
itself converted automatically to a segmented address.
Several new/modified files are supplied:
CICS32TC.CMD Translates, compiles and links a 32-bit C CICS OS/2
program
CICS32CL.CMD Compiles and/or links a translated 32-bit C CICS OS/2
program
FAACLIB.LIB Modified library containing 32-bit C interface code
FAACSTRT.H Modified C CICS OS/2 program header file
FAAECIH.H Modified ECI header file
FAAMSPTR.EXE Modified map translator to give packed structures
Note that when a 32-bit CICS OS/2 transaction is built, the linker may
give a warning message:
warning L4008: aliased fix-up to non-alias object near 2 in object
SEG16T__faaistrt
This message may safely be ignored.
Debugging using IPMD.
This is enabled by using the following startup option:
CICSRUN /D-V123(IPMD)
where 'V123' is the name of the terminal to be debugged.
The program to be debugged should be compiled with the '/Ti' option.
This option can be added to the 'CICSICC' environment variable, if the
program is compiled using 'CICS32TC' or 'CICS32CL'.
If it is separately linked using 'link386', the '/CO' option is also
required.
5
When the IPMD logo is displayed, 'OK' should be selected to continue.
When the disassembly window appears, at the debug session controls
window, select
'Options'
'Session Settings'
'PM Debugging Mode'
'Asynchronous'
At the disassembly window, select
'breakpoints'
'set'
'type' 'load'
'parameters' 'faalspdl.dll'
'OK'
'run'
'run'
This sets a breakpoint on the CLOG program, and continues to run the
task to allow that terminal and the rest of CICS OS/2 to come up. (If
IPMD were to be shut down, e.g. by typing 'exit' in the debug terminal
window, before CICS OS/2 was shut down, and the option to save restart
information were to be chosen, then this breakpoint information and
other profile information would be saved by IPMD and would not have to
be entered each time CICS OS/2 was started using IPMD.)
The debugger must hit a breakpoint to stop execution of the task before
further breakpoints can be set. When a program is required to be
debugged, the debugger can be activated by running 'CLOG', which will
hit the breakpoint set on loading of the 'CLOG' program. A further
breakpoint on loading of the user's DLL can then be selected, in a
similar fashion to the breakpoint on loading of 'faalspdl.dll'. Once
the user program is loaded, a breakpoint on the source line can be
selected using the 'debug session controls' window.
'OK' (Clear the breakpoint message)
'Threads'
'2 Enabled runnable' (Select the main thread)
'Program parts'
'userapp.dll' (the user's dll)
'File'
'Open As'
'Source'
A breakpoint can then be set as normal on the required source line.
Debugging then proceeds as for normal under IPMD.
Note that a breakpoint could be set directly on the loading of the
user's program at IPMD startup, or on another program instead of
FAALSPDL. The advantage of the indirect approach is that it is easy
to activate the debugger at any time by typing 'CLOG' on the terminal.
'CLOG' is a temporarily resident program, so is loaded each time it is
used, so a load breakpoint will be activated at this point.
Note that no breakpoints (except 'load') should be left in a module
when the program ends if the module may be unloaded, as with the
CSD 22 version of IPMD problems may arise if the module is reloaded
with breakpoints already set inside it.
6
User exits
There is no support for user exits written using IBM C Set/2.
External Transaction Initiation
There is no support for ETI using IBM C Set/2.
External import/export
There is no support for the use of external import/export routines
'FAAImport' and 'FAAExport' with IBM C Set/2.
External Field Setting
There is no support for the use of the field setting procedure
'FaaSetTableField' with IBM C Set/2.
**************************************************************
**************************************************************
*** ***
*** End of PTF 25 updates. ***
*** Updates for previous PTFs follow. ***
*** ***
**************************************************************
**************************************************************
i
README.TXT FOR
CICS OS/2 1.2.0 SERVICE LEVEL 24
19 February 1993
TABLE OF CONTENTS
─────────────────
Introduction . . . . . . . . . . . . . . . . . . . . . 1
Current Level . . . . . . . . . . . . . . . . . . . . . 1
Hints and other information. . . . . . . . . . . . . . 1
Changes due to fix for APAR PN36110. . . . . . . . . . . 2
1
INTRODUCTION
────────────
CURRENT LEVEL
─────────────
The current level of CICS OS/2 is 1.2.0. Service Level 24.
HINTS AND OTHER INFORMATION.
────────────────────────────
Required Import Groups
──────────────────────
The following is a table which indicates the import groups introduced at
each PTF level. Systems being upgraded from a previous PTF level may require
to import screen file changes. For example a customer upgrading from PTF
level 18 to the current level would require to import groups PN21505,
PN28420 and PN29610.
┌─────────────┬────────────────────────────────────────────────────────────┐
│ PTF level │ Import Group(s) │
├─────────────┼────────────────────────────────────────────────────────────┤
│ 1 │ PL61234, PL61239 │
├─────────────┼────────────────────────────────────────────────────────────┤
│ 8 │ PL71166, PL81305 │
├─────────────┼────────────────────────────────────────────────────────────┤
│ 17 │ PN15480 │
├─────────────┼────────────────────────────────────────────────────────────┤
│ 19 │ PN21505, PN28420 │
├─────────────┼────────────────────────────────────────────────────────────┤
│ 21 │ PN29610 │
└─────────────┴────────────────────────────────────────────────────────────┘
2
Changes due to fix for APAR PN36110
───────────────────────────────────
As part of this APAR fix the following trace points have been
added to the product.
┌─────────┬──────────────────────┬───────────────────────────────────┐
│ ID = 01 │ Issued by FAASRCKC │ Task Control │
├─────────┼──────────────────────┼─────────────────┬─────────────────┤
│ TYPE / │ ENTRY DESCRIPTION │ FIELD A │ FIELD B │
│ POINT │ │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV K01 │ Starting ENQ/DEQ. │ │ Function Code │
├─────────┼──────────────────────┼─────────────────┴─────────────────┤
│ MV K02 │ Request to gbl task. │ ENQ resource name / address │
└─────────┴──────────────────────┴───────────────────────────────────┘
**************************************************************
**************************************************************
*** ***
*** End of PTF 24 updates. ***
*** Updates for previous PTFs follow. ***
*** ***
**************************************************************
**************************************************************
i
README.TXT FOR
CICS OS/2 1.2.0 SERVICE LEVEL 23
25 January 1993
TABLE OF CONTENTS
─────────────────
Introduction . . . . . . . . . . . . . . . . . . . . . 1
Current Level . . . . . . . . . . . . . . . . . . . . . 1
Hints and other information. . . . . . . . . . . . . . 1
Changes due to fix for APAR PN27866 . . . . . . . . . . 2
Notes for implementation of APAR PN13891. . . . . . . . 3
1
INTRODUCTION
────────────
CURRENT LEVEL
─────────────
The current level of CICS OS/2 is 1.2.0. Service Level 23.
HINTS AND OTHER INFORMATION.
────────────────────────────
Required Import Groups
──────────────────────
The following is a table which indicates the import groups introduced at
each PTF level. Systems being upgraded from a previous PTF level may require
to import screen file changes. For example a customer upgrading from PTF
level 18 to the current level would require to import groups PN21505,
PN28420 and PN29610.
┌─────────────┬────────────────────────────────────────────────────────────┐
│ PTF level │ Import Group(s) │
├─────────────┼────────────────────────────────────────────────────────────┤
│ 1 │ PL61234, PL61239 │
├─────────────┼────────────────────────────────────────────────────────────┤
│ 8 │ PL71166, PL81305 │
├─────────────┼────────────────────────────────────────────────────────────┤
│ 17 │ PN15480 │
├─────────────┼────────────────────────────────────────────────────────────┤
│ 19 │ PN21505, PN28420 │
├─────────────┼────────────────────────────────────────────────────────────┤
│ 21 │ PN29610 │
└─────────────┴────────────────────────────────────────────────────────────┘
2
Changes due to fix for APAR PN27866
───────────────────────────────────
A new version of the run-time library COBLIB.DLL V3.0.54 has been
shipped as part of this APAR fix. This is used by CICS OS/2 and by
default is placed in the CICS120\OS2DSD directory.
NOTE:
╔══════════════════════════════════════════════════════╗
║ This version of the run-time library is INCOMPATIBLE ║
║ with ANIMATOR debugger tool shipped with IBM COBOL/2 ║
║ and some earlier versions of Micro Focus COBOL. ║
╚══════════════════════════════════════════════════════╝
Your LIBPATH environment variable in CONFIG.SYS should point
to this newly shipped version of COBLIB.DLL in preference to any
earlier version of this file, for example which may be part of a
COBOL/2 or MF COBOL 2.5 directory.
Your CICSWRK environment variable should be used to reference a COBOL
directory which contains an appropriate level of the ANIMATOR program
ANIMATE.EXE. For example with MF COBOL V3.0.54 this might be
SET CICSWRK=D:\CICS120\OS2DSD;D:\CICS120\USERDSD;D:\COBOL\EXEDLL
Animator/2 Support
Animator/2 is a Presentation Manager version of Animator, available
with the MicroFocus Workbench Version 3. The PATH, LIBPATH, COBDIR,
and COBHNF environment variables must be set as described in the
MicroFocus COBOL documentation.
To start CICS OS/2 with Animator/2, enter -
CICSRUN /D-V123(ANIMPM)
Restriction: The "Check" function of Animator/2 is not supported; this
function recompiles the program from within the debugger,
and results in a Trap if used under CICS OS/2.
3
Notes for implementation of APAR PN13891
────────────────────────────────────────
Two additional source files are shipped with PTF23 they are
FAAUTPUC.CCP (Source code)
FAAUTWUC.CBL (Source copybook).
They are example code to allow the conversion of data from a host
to CICS OS/2 during function shipping. This user code is called
from the CICS OS/2 system conversion routine FAAUTPSC. The default
supplied code does not translate data but may be used as a template
and changed to allow customer specific data conversion.
To invoke the call from FAAUTPSC to this user defined routine requires
three steps:
The supplied code FAAUTPUC.CCP must be modified as appropriate,
translated, compiled and linked.
A user conversion table must be created using the supplied routine
CICSLCTB.CMD. This may be a SBCS or DBCS conversion table.
Examples of this are the host DFHCCNV conversion macros.
An appropriate SIT entry must be created to point to this
conversion table with the 'User Conversion Table' entry. This
field should be a fully qualified file path and file name.
For more information please see the System and Application Guide
Chapter 20 'Communications: data conversion'.
**************************************************************
**************************************************************
*** ***
*** End of PTF 23 updates. ***
*** Updates for previous PTFs follow. ***
*** ***
**************************************************************
**************************************************************
i
README.TXT FOR
CICS OS/2 1.2.0 SERVICE LEVEL 22
1 January 1993
TABLE OF CONTENTS
─────────────────
Introduction . . . . . . . . . . . . . . . . . . . . . 1
Current Level . . . . . . . . . . . . . . . . . . . . . 1
Hints and other information. . . . . . . . . . . . . . 1
Changes due to fix for APAR PN21507 . . . . . . . . . . 1
1
INTRODUCTION
────────────
CURRENT LEVEL
─────────────
The current level of CICS OS/2 is 1.2.0. Service Level 22.
HINTS AND OTHER INFORMATION.
────────────────────────────
2
Changes due to fix for APAR PN21507
───────────────────────────────────
This APAR was created to allow NetBios peer to peer communication
in an OS/2 2.0 environment. A number of new and changed tracepoints
have been included. A full list of the NetBios tracepoints follows.
┌─────────┬──────────────────────┬───────────────────────────────────┐
│ ID = 80 │ Issued by FAANBSIN │ NetBios Listener │
├─────────┼──────────────────────┼─────────────────┬─────────────────┤
│ TYPE / │ ENTRY DESCRIPTION │ FIELD A │ FIELD B │
│ POINT │ │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MN M01 │NetBIOS Listener Entry│ Mode │ Adapter │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M02 │Initialization │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M03 │FAANBSPH Listener │ Adapter │ Adapter │
│ │Starting │ │ direction │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M04 │Adapter Thread Started│ OS/2 RC │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M05 │Adapter Thread Started│ OS/2 RC │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MO M06 │Failed to start │ Adapter │ OS/2 RC │
│ │Adapter Thread │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M07 │Finished Adapter │ OS/2 RC │ Living Adapters │
│ │Initialization │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M08 │Service Thread │ OS/2 RC │ │
│ │Notification │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M09 │Finished │ │ │
│ │Initialization │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M10 │Listener Active │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M11 │Failed to start │ │ │
│ │Listeners │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M12 │Tidy up Adapter │ │ │
│ │Threads │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M13 │Killing Adapter │ │ │
│ │Thread │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M14 │Adapter Thread Killed │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M15 │Adapter Threads │ │ │
│ │Terminated │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M16 │Stopping Adapter │ Adapter │ │
│ │Thread │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M17 │Adapter Thread Stopped│ OS/2 RC │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M18 │Stopping Service │ │ │
│ │Thread │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M19 │Service Thread Stopped│ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MX M20 │NetBIOS Listener Exit │ Return Code │ Adapter │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M21 │Create Thread │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M22 │Thread Creation │ OS/2 RC │ │
│ │Completed │ │ │
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
3
┌─────────┬──────────────────────┬─────────────────┬─────────────────┐
│ MO M23 │Semaphore Wait Failed │ OS/2 RC │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MO M24 │Thread Creation Failed│ OS/2 RC │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MO M25 │Thread Allocation │ OS/2 RC │ │
│ │Failed │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MO M26 │Failed to set │ OS/2 RC │ │
│ │thread Semaphore │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M27 │Thread Creation │ OS/2 RC │ │
│ │Completed │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M28 │Exit from Create │ Return Code │ │
│ │Thread │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M29 │Adapter Thread │ Adapter │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M30 │Adapter Thread │ OS/2 RC │ │
│ │DosCreateSem │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M31 │Adapter Reset Result │ OS/2 RC │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M32 │Limited Resources │ Connections │ Network Request │
│ │Being Used │ │ Blocks │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M33 │NetBIOS Status Result │ NetBIOS RC │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M34 │NetBIOS Name Added │ NetBIOS RC │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M35 │Adapter Listen Primed │ NetBIOS RC │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M36 │Adapter Thread Ready │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M37 │Broadcast Timer │ OS/2 RC │ Delay Time │
│ │Activated │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M38 │Adapter Thread │ Index │ │
│ │DosMuxSemWait │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M39 │Cancel Outstanding │ NRB Index │ │
│ │Commands │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M40 │Adapter Reset │ NetBIOS RC │ │
│ │Completed │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M41 │NetBIOS Add Name │ NetBIOS RC │ │
│ │Completed │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M42 │Adapter Listen │ NetBIOS RC │ │
│ │Reprimed │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M43 │Adapter Thread │ │ │
│ │Finishing │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M44 │Adapter Thread Stopped│ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M45 │Adapter Thread Finish │ Adapter │ │
│ │Notified │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M46 │Service Thread Entry │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M47 │DosCreateQueue in │ OS/2 RC │ │
│ │Service Thread │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M48 │DosCreateSem in │ OS/2 RC │ │
│ │Service Thread │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M49 │Service State Started │ │ │
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
4
┌─────────┬──────────────────────┬─────────────────┬─────────────────┐
│ MV M50 │Process Queue Elements│ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M51 │DosReadQueue in │ OS/2 RC │ │
│ │Service Thread │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M52 │Processing Queue │ Queue Element │ Queue Element │
│ │Element │ Address │ Action │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M53 │Unimplemented Queue │ │ Queue Element │
│ │Element Type │ │ Action │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M54 │Queue Element │ Return Code │ │
│ │Processed │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M55 │Service Thread │ │ │
│ │Finishing │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M56 │Service Thread Stopped│ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M57 │Service Thread │ Return Code │ │
│ │Completion │ │ │
│ │Notification │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M58 │Reset Adapter │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M59 │Reset Parameters │ Adapter │ Reset type │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M60 │NetBIOS Reset Result │ NetBIOS RC │ Reset Type │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MO M61 │Failed NetBIOS Reset │ NetBIOS RC │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M62 │Completed NetBIOS │ NetBIOS RC │ │
│ │Reset │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M63 │AddNetBIOSName Entry │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M64 │Exit from AddNetBIOS │ NetBIOS RC │ │
│ │Name │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M65 │PrimeAdapterListen │ Adapter Detail │ │
│ │Entry │ Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M66 │PrimeAdapterListen │ Return Code │ │
│ │Exit │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M67 │Initialise Control │ │ │
│ │Entries │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M68 │Local TCS Entry │ System │ │
│ │Details - 1 │ Identification │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M69 │Local TCS Entry │ Applid │ Applid(cont.) │
│ │Details - 2 │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M70 │Local TCS Entry │ Buffer Size │ Sessions │
│ │Details - 3 │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M71 │Local TCS Entry │ TctPrty │ Attach Security │
│ │Details - 4 │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M72 │Control Initialization│ │ │
│ │Completed │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M73 │Obtain NetBIOS Adapter│ │ │
│ │UAA │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MO M74 │Failed to Obtain │ NetBIOS RC │ │
│ │Status │ │ │
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
5
┌─────────┬──────────────────────┬─────────────────┬─────────────────┐
│ SX M75 │Obtained Adapter │ NetBIOS RC │ │
│ │Address │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M76 │Initialise Network │ Available NRBs │ │
│ │Request Blocks │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M77 │NRB Initialization │ │ │
│ │Completed │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M78 │Issue Broadcast │ │ │
│ │Notice to Clients │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M79 │Broadcast PDU │ Broadcast NCB │ │
│ │Constructed │ Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M80 │Broadcast Datagram │ NetBIOS RC │ │
│ │Result │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MO M81 │Failed to Broadcast │ NetBIOS RC │ │
│ │Datagram │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M82 │Datagram Broadcast │ NetBIOS RC │ │
│ │Completed │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M83 │Obtain Inbound │ │ │
│ │Connection │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M84 │Free Connection is │ │ │
│ │available │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M85 │Requeue as Instantiate│ │ │
│ │Inbound │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M86 │Unable to accept, │ │ │
│ │Just Hanging Up │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M87 │Exit from Inbound │ │ │
│ │Connection │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M88 │Instantiate Inbound │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M89 │Inbound Instantiate │ │ │
│ │Connection │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M90 │Allocate Receive Pool │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M91 │Receive Pool Allocated│ Return Code │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M92 │Prime Receive Any │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M93 │Exit from Prime │ NetBIOS RC │ │
│ │Receive Any │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M94 │Reprime Receive Any │ Network Control │ │
│ │ │ Block Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MO M95 │Failed to Reprime │ NetBIOS RC │ │
│ │Receive Any │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M96 │Exit from Reprime │ NetBIOS RC │ │
│ │Receive Any │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M97 │Tidy Adapter Resources│ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M98 │Found Active Session │ Session Control │ │
│ │ │ Block Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M99 │Adapter Tidy Completed│ │ │
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
6
┌────────────────────────────────────────────────────────────────────┐
│ ID = 81 Issued by FAANBSIN NetBios Listener │
├─────────┬──────────────────────┬─────────────────┬─────────────────┤
│ TYPE / │ ENTRY DESCRIPTION │ FIELD A │ FIELD B │
│ POINT │ │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M01 │ Entry to Generic │ Queue Element │ Queue Element │
│ │ Receive │ Pointer │ Action │
│ │ │ │ 1 Byte │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M02 │Inbound Version 2 PDU │ Protocol Version│ PDU Type │
│ │ │ │ 1 Byte │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M03 │ Old Protocol PDU │ Protocol Version│ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M04 │Exit from Generic │ Protocol Version│ │
│ │Receive │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M05 │Entry to Version 2 │ Queue Element │ Queue Element │
│ │Data Processing │ Pointer │ Action │
│ │ │ │ 1 Byte │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M06 │PDU Details - 1 │ PDU Type │ Session Id │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M07 │PDU Details - 2 │ User Data Length│ User Send Type │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M08 │PDU Details - 3 │ User Data Length│ NCB Length │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M09 │PDU Details - 4 │ NCB RC │ Completion RC │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M10 │PDU Details - 5 │ Session Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M11 │Last Flow seen, │ Session Pointer │ │
│ │tidy up Session │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M12 │Data held in temp. │ OS/2 RC │ │
│ │buffer │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M13 │Unable to hold data - │ Session Pointer │ │
│ │DosAlloc failed │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M14 │PDU Addresses │ PDU Pointer │ PDU beyond │
│ │ │ │ header Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M15 │Data PDU has no │ Session ID │ │
│ │session │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M16 │Exit from Version 2 │ Return Code │ │
│ │Data Processing │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M17 │Entry to Version 1 │ Queue Element │ Connection Ctrl │
│ │Data Processing │ Pointer │ Block Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M18 │Data has no Session │ │ │
│ │ │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M19 │Data PDU Details - 1 │ Flag │ Length │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M20 │Data PDU Details - 2 │ PDU Length │ NCB Length │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M21 │Data PDU Details - 3 │ NCB RC │ NCB Completion │
│ │ │ │ RC │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M22 │Data PDU Details - 4 │ Session Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M23 │Session has completed,│ Session Pointer │ │
│ │Tidy up │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M24 │DosAllocSeg for │ OS/2 RC │ │
│ │temporary buffer │ │ │
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
7
┌─────────┬──────────────────────┬─────────────────┬─────────────────┐
│ MV M25 │Unable to obtain │ Session Pointer │ │
│ │temporary │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M26 │Exit from Version 1 │ Return Code │ │
│ │Data Processing │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M27 │Obtain Outbound │ Queue Element │ │
│ │Connection Entry │ Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M28 │Unable to bind to │ │ │
│ │System Context Block │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M29 │Unable to find free │ │ │
│ │System or Connection │ │ │
│ │Context Block. │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M30 │System Context Block │ System Context │ │
│ │allocated │ Block Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M31 │System Call is Busy │ System Context │ │
│ │ │ Block Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M32 │System and Connection │ System Context │ Connection │
│ │Context Blocks │ Block Pointer │ Context │
│ │Allocated │ │ Block Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M33 │Queue Next Stage for │ Queue Element │ Queue Element │
│ │Connection │ Pointer │ Action │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M34 │Obtain Outbound │ │ │
│ │Connection │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M35 │Discard Connection │ Queue Element │ │
│ │ │ Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M36 │Found System Entry │ System Context │ First Connection│
│ │ │ Block Pointer │ Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M37 │System context │ Queue Element RC│ │
│ │deallocated │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M38 │Discard Connection │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M39 │Obtain Network │ Queue Element │ Adapter │
│ │Request Block │ Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M40 │Chain request due to │ Queue Element │ Queue Element │
│ │busy condition │ Pointer │ Action │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M41 │Requeue Queue Element │ Queue Element │ Queue Element │
│ │ │ Pointer │ Action │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M42 │Obtain Network │ │ │
│ │Request Block │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M43 │Issue Call │ Queue Element │ Adapter │
│ │ │ Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M44 │Calling Parameters - 1│ Callname │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M45 │Calling Parameters - 2│ Callname │ │
│ │ │ (continued) │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M46 │NetBIOS Call Result │ NetBIOS RC │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MO M47 │Unable to queue │ NetBIOS RC │ │
│ │NetBIOS Call │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M48 │Issue Call │ │ │
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
8
┌─────────┬──────────────────────┬─────────────────┬─────────────────┐
│ SN M49 │Call Result │ Queue Element │ │
│ │ │ Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M50 │Command Completion │ Queue Element │ │
│ │Status Checking │ Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M51 │NetBIOS Call Details │ Adapter │ Logical Session │
│ │ │ │ Number │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M52 │Remote Applid from │ Applid │ │
│ │Version 1 PDU │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M53 │Local System │ System Id │ │
│ │Details - 1 │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M54 │Local System │ Applid │ Applid(cont.) │
│ │Details - 2 │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M55 │Remote Applid from │ Applid │ Applid(cont.) │
│ │Version 2 PDU │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M56 │NetBIOS Send Result │ NetBIOS RC │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M57 │Call Failure │ NetBIOS RC │ NetBIOS NCB │
│ │ │ │ Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M58 │Call Result │ Queue Element │ │
│ │ │ Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M59 │Reject Outbound │ Queue Element │ │
│ │ │ Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M60 │Reject Outbound │ Queue Element │ │
│ │ │ Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M61 │Adapter Died │ Queue Element │ │
│ │ │ Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M62 │Adapter Died │ Queue Element │ │
│ │ │ Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M63 │Connect Termination │ Queue Element │ │
│ │ │ Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M64 │Connect Termination │ Queue Element │ │
│ │ │ Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M65 │Version 1 Connect │ Queue Element │ Connection │
│ │ │ Pointer │ Context Block │
│ │ │ │ Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M66 │Version 1 Connect │ Applid │ Applid(cont.) │
│ │Details - 1 │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M67 │Version 1 Connect │ Transid │ │
│ │Details - 2 │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M68 │Obtained Session │ Session Context │ │
│ │Context Block │ Block Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M69 │Failed to queue │ │ │
│ │ICE Entry │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M70 │NetBIOS Send for │ NetBIOS RC │ NCB Pointer │
│ │Connect Response │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M71 │Version 1 Connect │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M72 │Add ICE Entry │ Session/System │ Session/System │
│ │ │ Identification │ Index │
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
9
┌─────────┬──────────────────────┬─────────────────┬─────────────────┐
│ MV M73 │ICE Entry Start Time │ Time │ Time(cont.) │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M74 │ICE Table is very busy│ Start Next │ Start Max │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M75 │ICE Entry Obtained │ Start Next │ ICE Entry │
│ │ │ │ Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M76 │ICE Entry Shuffle │ Source Pointer │ Destination │
│ │ │ │ Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M77 │ICE Entry Insertion │ OS/2 RC │ │
│ │Complete │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M78 │Insert ICE Entry │ Return Code │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M79 │Discard Connection │ Connection │ │
│ │ │ Context │ │
│ │ │ Block Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M80 │Free queued elements │ Connection │ Session Context │
│ │for session │ Context │ Block Pointer │
│ │ │ Block Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M81 │Free QElement Details │ Queue Element │ Queue Element │
│ │ │ Pointer │ Action │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M82 │Drop connection │ Context Control │ System Control │
│ │association │ Block Pointer │ Block Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M83 │Remove system and │ System Control │ First Connection│
│ │connection association│ Block Pointer │ Control │
│ │ │ │ Block Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M84 │Match at first │ Next Connection │ First Connection│
│ │connection │ Control │ Control │
│ │ │ Block Pointer │ Block Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M85 │Searching down │ Next Connection │ First Connection│
│ │connection chain - 1 │ Control │ Control │
│ │ │ Block Pointer │ Block Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M86 │Searching down │ Next Connection │ Connection │
│ │connection chain - 2 │ Control │ Control │
│ │ │ Block Pointer │ Block Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M87 │Searching down │ Next Connection │ Connection │
│ │connection chain - 3 │ Control │ Control │
│ │ │ Block Pointer │ Block Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M88 │Now unlinked from │ System first │ Local System │
│ │system entry │ Connection │ Context │
│ │ │ Context │ Block Pointer │
│ │ │ Block Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M89 │Discard Connection │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M90 │Install System │ Queue Element │ │
│ │ │ Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M91 │Install System Result │ Return Code │ Request Block │
│ │ │ │ Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M92 │Reply Ready │ Return Code │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M93 │Buffer Addresses │ Queue Elements │ │
│ │ │ Buffer Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M94 │Install System │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M95 │Issue Connect Response│ Queue Element │ │
│ │ │ Pointer │ │
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
10
┌─────────┬──────────────────────┬─────────────────┬─────────────────┐
│ MV M96 │Send Connect Response │ Queue Element │ │
│ │ │ Action │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M97 │Result from NetBIOS │ NetBIOS RC │ │
│ │Send │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M98 │Sent Connect Response │ Queue Element │ │
│ │ │ Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M99 │Sent Connect Response │ │ │
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
11
┌────────────────────────────────────────────────────────────────────┐
│ ID = 82 Issued by FAANBSIN NetBios Listener │
├─────────┬──────────────────────┬─────────────────┬─────────────────┤
│ TYPE / │ ENTRY DESCRIPTION │ FIELD A │ FIELD B │
│ POINT │ │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M01 │Sent Version 1 │ Queue Element │ Queue Element │
│ │Connect Response │ Pointer │ RC │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M02 │Sent Version 1 │ │ │
│ │Connect Response │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M03 │Free Network Request │ Queue Element │ │
│ │Block │ Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M04 │Free Network Request │ │ │
│ │Block │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M05 │Locate System │ Applid Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M06 │Locate System │ System Context │ │
│ │ │ Block Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M07 │Insert System │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M08 │Insert System │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M09 │Sent Connect Request │ Queue Element │ Queue Element │
│ │ │ Pointer │ RC │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M10 │Sent Connect Request │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M11 │Process Version 2 │ Queue Element │ Connection │
│ │Connect │ Pointer │ Context Block │
│ │ │ │ Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M12 │Connect Details - 1 │ Local System │ Originator Type │
│ │ │ Details Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M13 │Connect Details - 2 │ Sessions In │ Sessions Out │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MO M14 │Failed to queue new │ │ │
│ │ICE Entry │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M15 │Process Version 2 │ │ │
│ │Connect │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M16 │Process Version 2 │ Queue Element │ Connection │
│ │Connect Response │ Pointer │ Context Block │
│ │ │ │ Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M17 │Process Version 2 │ Return Code │ │
│ │Connect Response │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M18 │Process Version 1 │ Queue Element │ Connection │
│ │Connect │ Pointer │ Context Block │
│ │ │ │ Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M19 │Process Version 1 │ Return Code │ │
│ │Connect │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M20 │Initiate Out Session │ Queue Element │ │
│ │ │ Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M21 │Located System and │ System Context │ Connection │
│ │Connection Blocks │ Block Pointer │ Context Block │
│ │ │ │ Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M22 │Allocated Session │ Session Context │ Already Active │
│ │Blocks │ Block Pointer │ Indication │
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
12
┌─────────┬──────────────────────┬─────────────────┬─────────────────┐
│ MV M23 │Session Details │ Index │ Integrity │
│ │ │ │ Check │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M24 │Protocol Session │ Session Id │ │
│ │Identification │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M25 │Initiate Out Session │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M26 │Instantiate Version 1 │ Queue Element │ │
│ │Protocol │ Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M27 │System Search │ System Context │ Connection │
│ │Completed │ Block Pointer │ Context Block │
│ │ │ │ Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M28 │Session Details │ Index │ Integrity Check │
│ │Established │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M29 │Instantiate Version 1 │ │ │
│ │Protocol │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M30 │Issue Attach │ Queue Element │ Queue Element │
│ │ │ Pointer │ Action │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M31 │NetBIOS Send Attach │ NetBIOS RC │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M32 │Issue Attach │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M33 │Sent Attach │ Queue Element │ Queue Element │
│ │ │ Pointer │ RC │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M34 │Sent Attach │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M35 │Issue Version 2 Abend │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M36 │NetBIOS Send Abend │ NetBIOS RC │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M37 │Issue Version 2 Abend │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M38 │Process Version 2 │ Queue Element │ Connection │
│ │Attach │ Pointer │ Control Block │
│ │ │ │ Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M39 │Attach Details - 1 │ Transaction Id │ Session Id │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M40 │Attach Details - 2 │ User Data Length│ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M41 │Obtained Buffer from │ OS/2 RC │ │
│ │DosAllocSeg │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M42 │Obtained Session │ Session Context │ │
│ │Context Block │ Block Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M43 │Linked Session │ Session Context │ │
│ │Context Block │ Block Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M44 │Transfer of User Data │ PDU │ PDU Pointer │
│ │ │ Pointer │ beyond header │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M45 │Version 2 Protocol │ Return Code │ │
│ │Attach │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M46 │Identify Session │ Queue Element │ Queue Element │
│ │ │ Pointer │ Action │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M47 │Found System Entry │ System Context │ │
│ │ │ Block Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M48 │Assume System Details │ Applid │ Applid(cont.) │
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
13
┌─────────┬──────────────────────┬─────────────────┬─────────────────┐
│ SX M49 │Identify Session │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M50 │Discard Session │ Queue Element │ Queue Element │
│ │ │ Pointer │ Action │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M51 │Discard Session │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M52 │Receive Data │ Queue Element │ Queue Element │
│ │ │ Pointer │ Action │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M53 │Queue Element Details │ Index │ Integrity Check │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M54 │Queue Element in chain│ Queue Element │ │
│ │ │ Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M55 │Receive Data │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M56 │Identify System │ Queue Element │ Queue Element │
│ │ │ Pointer │ Action │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M57 │Identify System │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M58 │Release System │ Queue Element │ Queue Element │
│ │ │ Pointer │ Action │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M59 │Release System │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M60 │Send Data │ Queue Element │ Queue Element │
│ │ │ Pointer │ Action │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M61 │Send Data │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M62 │Send Data │ Queue Element │ Queue Element │
│ │ │ Pointer │ Action │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M63 │Send Data Details │ User Data Length│ Protocol Version│
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M64 │NetBIOS Send Data │ NetBIOS RC │ NCB Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M65 │Send Data │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M66 │Sent Version 1 │ Queue Element │ Queue Element │
│ │Preamble │ Pointer │ Action │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M67 │ Preamble Details │ User Data Length│ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M68 │ NetBIOS Send Preamble│ NetBIOS RC │ NCB Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M69 │ Send Version 1 │ │ │
│ │ Preamble │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M70 │ Sent Version 1 Data │ Queue Element │ Queue Element │
│ │ │ Pointer │ RC │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M71 │ Sent Version 1 Data │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M72 │ Sent Version 2 Data │ Queue Element │ Queue Element │
│ │ │ Pointer │ RC │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M73 │ Sent Version 2 Data │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M74 │ Discard Session │ Session Context │ │
│ │ │ Block Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M75 │ Requeue Active │ Queue Element │ │
│ │ Calling Elements │ Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M76 │ Discard Session │ │ │
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
14
┌─────────┬──────────────────────┬─────────────────┬─────────────────┐
│ SN M77 │ Process Version 2 │ Queue Element │ Connection │
│ │ Abend │ Pointer │ Control Block │
│ │ │ │ Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M78 │ Abend Details │ PDU Type │ Session Id │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M79 │ Process Version 2 │ Return Code │ │
│ │ Abend │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M80 │ Process Version 2 │ Queue Element │ Connection │
│ │ Close │ Pointer │ Control Block │
│ │ │ │ Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M81 │ Close Details │ PDU Type │ Reason │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M82 │ Process Version 2 │ Return Code │ │
│ │ Close │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M83 │ Output Console │ Message Number │ │
│ │ Message │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M84 │ Console Buffer │ OS/2 RC │ │
│ │ from DosAllocSeg │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M85 │ Output Console │ │ │
│ │ Message │ │ │
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
15
┌────────────────────────────────────────────────────────────────────┐
│ ID = 83 Issued by FAANBSPH NetBios Protocol Handler │
├─────────┬──────────────────────┬─────────────────┬─────────────────┤
│ TYPE / │ ENTRY DESCRIPTION │ FIELD A │ FIELD B │
│ POINT │ │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MN M01 │NetBIOS Protocol │ FMH Pointer │ CSA2 Pointer │
│ │Handler │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M02 │DosOpenQueue Status │ OS/2 RC │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M03 │DosOpenSem Status │ OS/2 RC │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M04 │Queue Element │ OS/2 RC │ │
│ │DosAllocSeg Status │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M05 │Queue Element │ OS/2 RC │ │
│ │DosGiveSeg Status │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M06 │Scratch Buffer │ OS/2 RC │ │
│ │DosAllocSeg Status │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M07 │Scratch Buffer │ OS/2 RC │ │
│ │DosGiveSeg Status │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M08 │Allocated Queue │ Queue Element │ │
│ │Element │ Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M09 │Internal Primer Event │ Major Event │ Minor Event │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M10 │Protocol Operation │ FMH Pointer │ FMH Operation │
│ │Required │ │ 1 Byte │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MX M11 │Protocol Operation │ Conversation │ Requested │
│ │Details │ State 1 Byte │ Operation 1 Byte│
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MX M12 │Fixup Status Code │ Raw Status │ │
│ │ │ 2 Bytes │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MX M13 │NetBIOS Protocol │ Status │ │
│ │Handler │ 2 Bytes │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M14 │Receive* │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M15 │Receive Details │ FMH Request │ FMH Send Type │
│ │ │ Length │ 1 Byte │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M16 │Receive │ Status │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M17 │Send Allocate │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M18 │Send Allocate │ Applid │ Applid(cont.) │
│ │Details - 1 │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M19 │Send Allocate │ Applid(cont.) │ Applid(cont.) │
│ │Details - 2 │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M20 │Send Allocate │ FMH Request │ │
│ │Details - 3 │ Length │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M21 │Allocated Session │ Index │ Integrity Check │
│ │Details │ │ │
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
16
┌─────────┬──────────────────────┬─────────────────┬─────────────────┐
│ SX M22 │Send Allocate │ Status │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M23 │Send │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M24 │Send Details │ FMH Request │ │
│ │ │ Length │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M25 │Send │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M26 │Send Last │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M27 │Send Last │ Status │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M28 │Send Error │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M29 │Send Error │ Status │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M30 │Send Abend │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M31 │Send Abend │ Status │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M32 │Receive Allocate │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M33 │About to identify │ Index │ Integrity Check │
│ │Session │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M34 │Receive Allocate │ Status │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M35 │Install System │ Queue Element │ Queue Element │
│ │ │ Pointer │ Buffer Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M36 │Remote System │ Sessions │ Buffer Size │
│ │Details - 1 │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M37 │Remote System │ UAA │ UAA │
│ │Details - 2 │ (First 4 Bytes) │ (Last 2 Bytes) │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M38 │Remote System │ System Id │ Originator Type │
│ │Details - 3 │ │ 1 Byte │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M39 │Remote System │ Applid │ Applid(cont.) │
│ │Details - 4 │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M40 │Remote System │ Tct Prty │ Attach Security │
│ │Details - 5 │ │ 1 Byte │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M41 │About to call │ │ │
│ │User Exit 21 │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M42 │Returned from │ │ │
│ │User Exit 21 │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M43 │Result from │ Queue Element RC│ │
│ │Install Attempt │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M44 │Install System │ Status │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M45 │Delete System │ Queue Element │ Queue Element │
│ │ │ Pointer │ Buffer Pointer │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M46 │Release System │ Sessions │ Buffer Size │
│ │Details - 1 │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M47 │Release System │ UAA │ UAA │
│ │Details - 2 │ (First 4 Bytes) │ (Last 2 Bytes) │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M48 │Release System │ System Id │ Originator Type │
│ │Details - 3 │ │ 1 Byte │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M49 │Release System │ Applid │ Applid(cont.) │
│ │Details - 4 │ │ │
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
17
┌─────────┬──────────────────────┬─────────────────┬─────────────────┐
│ MV M50 │Release System │ Tct Prty │ Attach Security │
│ │Details - 5 │ │ 1 Byte │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M51 │About to call │ │ │
│ │User Exit 21 │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M52 │Returned from │ │ │
│ │User Exit 21 │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M53 │Delete System │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M54 │Set Connection │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M55 │Set Connection │ Applid │ Applid(cont.) │
│ │Details - 1 │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M56 │Set Connection │ System Id │ │
│ │Details - 2 │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M57 │Set Connection │ Status │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M58 │Release Connection │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M59 │Release Connection │ Applid │ Applid(cont.) │
│ │Details │ │ │
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
18
┌────────────────────────────────────────────────────────────────────┐
│ ID = 84 Issued by FAANBSAS NetBios Async Completion Module │
├─────────┬──────────────────────┬─────────────────┬─────────────────┤
│ TYPE / │ ENTRY DESCRIPTION │ FIELD A │ FIELD B │
│ POINT │ │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M01 │ Async Completion │ Post Type │ Return Code │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M02 │ NCB Details │ NCB Pointer │ NetBIOS Command │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M03 │ NCB Status │ NCB RC │ NCB Completion │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M04 │Connection Termination│ Queue Element │ Queue Element │
│ │ │ Pointer │ Action │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M05 │ Incoming Data │ Queue Element │Post Queue Handle│
│ │ from Receive Any │ Pointer │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ MV M06 │ Moved onto action │ OS/2 Return Code│ │
│ │ Queue │ │ │
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
19
**************************************************************
**************************************************************
*** ***
*** End of PTF 22 updates. ***
*** Updates for previous PTFs follow. ***
*** ***
**************************************************************
**************************************************************
i
README.TXT FOR
CICS OS/2 1.2.0 SERVICE LEVEL 21
16 November 1992
TABLE OF CONTENTS
─────────────────
Introduction . . . . . . . . . . . . . . . . . . . . . 1
Current Level . . . . . . . . . . . . . . . . . . . . . 1
Hints and other information. . . . . . . . . . . . . . 1
Changes due to fix for APAR PN24821 . . . . . . . . . . 1
Changes due to fix for APAR PN29610 . . . . . . . . . . 2
Restrictions on use of the /DOS command . . . . . . . . 3
1
INTRODUCTION
────────────
CURRENT LEVEL
─────────────
The current level of CICS OS/2 is 1.2.0. Service Level 21.
HINTS AND OTHER INFORMATION.
────────────────────────────
Changes due to fix for APAR PN24821
───────────────────────────────────
APAR PN24821 describes a problem where STARTBR and READNEXT on relative
record data sets (RRDS files) return an incorrect record.
The fix for PN24821 corrects this problem by changing the internal structure
of RRDS files. When CICS OS/2 starts up the control file is scanned to set
up, amongst other things, FCT entries. Should an RRDS file be encountered
which uses old-style internal structure then a warning message is issued
indicating that the file is out of date. To update the RRDS file use the
RRDS file converter which is provided as part of PTF21.
**WARNING** Before using the RRDS file converter routine ensure **WARNING**
**WARNING** that you have made security copies of all of your **WARNING**
**WARNING** data files. ie. All files with a file type .BTR **WARNING**
The RRDS converter routine can be invoked using the new command file
provided, CICSRRDS.CMD for an OS/2 environment or CICSRRDS.BAT for
a DOS environment. The routine will scan the CICS OS/2 control file
searching for RRDS file descriptions and converting these files.
The format of the command for RRDS file conversion is:
CICSRRDS [/B:nnnn] [/M:nnnn]
The converter routine accepts the /B and /M (file control) parameters
as used when starting up CICS OS/2. These options should only be used
if they are normally used during the startup of CICS OS/2. For more
information on these options refer to the CICS OS/2 System and Application
Guide Chapter 11.
2
CHANGES DUE TO FIX FOR APAR PN29610.
────────────────────────────────────
This PTF adds double byte character set code page support for OS/2 T
(Traditional Chinese) for Taiwan and OS/2 H (Hanguel) for Korea. The
new code pages supported are for OS/2 T: 938, 948; and
for OS/2 H: 934, 944.
The CEDA TCT definition transaction has been enhanced to allow selection
of the additional code pages when a DBCS terminal is defined. A Japanese,
Taiwanese or Korean terminal is selected using option J, for a DBCS terminal, and the
appropriate code page.
Existing Japanese users may notice that in some places in the CEDA and help
panels the terminal type is now described as 'DBCS' rather than 'Japanese'.
The actual definitions for Japanese terminals are unchanged, and will continue
to work as before.
Transaction routing is supported with these code pages. Data is converted to
EBCDIC for transmission over the link, using for OS/2 T: code page 937; and
for OS/2 H: code page 933.
Function shipping inbound to CICS OS/2 is also supported for OS/2 T and
OS/2 H. In the CEDA CVT definition panel there are some additional selection
for code page pairs. These selections are:
6: For the ASCII-EBCDIC code page pair 938,937 (OS/2 T only)
7: For the ASCII-EBCDIC code page pair 948,937 (OS/2 T only)
8: For the ASCII-EBCDIC code page pair 934,933 (OS/2 H only)
9: For the ASCII-EBCDIC code page pair 944,933 (OS/2 H only)
Function shipping to Host CICS for code pages 938, 948, 934, 944 can be done
using user defined data conversion tables on the host.
Additional tracepoints:
┌────────────────────────────────────────────────────────────────────┐
│ ID = 62 Issued by FAAO6STR Inbound transaction routing module. │
├─────────┬──────────────────────┬─────────────────┬─────────────────┤
│ TYPE / │ ENTRY DESCRIPTION │ FIELD A │ FIELD B │
│ POINT │ │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN T21 │ Enter ASCII-EBCDIC │ 2Byte Code Page │ 2Byte Length │
│ │ translation. │ from. │ 1Byte TCT-FLAG1 │
│ │ │ 2Byte Code Page │ 1Byte = zero │
│ │ │ to. │ │
│ │ │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX T22 │ Exit ASCII-EBCDIC │ 2Byte Code Page │ 2Byte Input │
│ │ translation. │ from. │ Length. │
│ │ │ 2Byte Code Page │ 2Byte Output │
│ │ │ to. │ Length. │
│ │ │ │ │
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
3
RESTRICTIONS ON USE OF THE /DOS COMMAND
───────────────────────────────────────
The use of the /DOS transaction, which is used from CICS OS/2 to start
a windowed OS/2 command session, is restricted to one active window
at any one time. That is, if a user has two CICS PM sessions only one can
successfully invoke the /DOS transaction at one time.
In addition if the user has a full screen terminal defined use of the
/DOS command is restricted to that full screen terminal.
Also, if the /DOS transaction is invoked and an OS/2 command session is
active CICS OS/2 will wait for that session to terminate before shutting
down when the CQIT command is used.
4
**************************************************************
**************************************************************
*** ***
*** End of PTF 21 updates. ***
*** Updates for previous PTFs follow. ***
*** ***
**************************************************************
**************************************************************
i
README.TXT FOR
CICS OS/2 1.2.0 SERVICE LEVEL 20
19 October 1992
TABLE OF CONTENTS
─────────────────
Introduction . . . . . . . . . . . . . . . . . . . . . 1
Current Level . . . . . . . . . . . . . . . . . . . . . 1
Hints and other information. . . . . . . . . . . . . . 1
Changes due to fix for APAR PN28669 . . . . . . . . . . 1
1
INTRODUCTION
────────────
CURRENT LEVEL
─────────────
The current level of CICS OS/2 is 1.2.0. Service Level 20.
HINTS AND OTHER INFORMATION.
────────────────────────────
Changes due to fix for APAR PN28669
───────────────────────────────────
Users experiencing the problem reported in APAR PN28669 should re-compile
and re-link any affected 'C' applications.
2
**************************************************************
**************************************************************
*** ***
*** End of PTF 20 updates. ***
*** Updates for previous PTFs follow. ***
*** ***
**************************************************************
**************************************************************
i
README.TXT FOR
CICS OS/2 1.2.0 SERVICE LEVEL 19
16 September 1992
TABLE OF CONTENTS
─────────────────
Introduction . . . . . . . . . . . . . . . . . . . . . 1
Current Level . . . . . . . . . . . . . . . . . . . . . 1
Hints and other information. . . . . . . . . . . . . . 1
Changes due to fix for APAR PN21505 (DPL) . . . . . . . 1
Changes due to fix for APAR PN27302 (CVT) . . . . . . . 3
1
INTRODUCTION
────────────
CURRENT LEVEL
─────────────
The current level of CICS OS/2 is 1.2.0. Service Level 19.
HINTS AND OTHER INFORMATION.
────────────────────────────
Changes due to fix for APAR PN21505 (DPL Extensions)
────────────────────────────────────────────────────
APAR PN21505 implements the extensions to DPL as defined in CICS/ESA 3.3;
the new command format is -
EXEC CICS LINK
PROGRAM(name)
[COMMAREA(data-area) [LENGTH(data-value)] [DATALENGTH(data-value]]
[SYSID(name)] [SYNCONRETURN] [TRANSID(name)]
The new options are -
DATALENGTH(data-value) If a COMMAREA is passed on a distributed link, then
the actual data transmitted will be the length in the
LENGTH parameter, null-truncated; if DATALENGTH is
specified, however, this will be the length of the
data transmitted regardless of content. This is a
performance option. Note, the COMMAREA received by
the server (linked-to) program is always LENGTH bytes
long.
SYNCONRETURN Without this option, any updates on the server side of
the link will not be committed until the client trans-
action issues a SYNCPOINT (explicitly or implicitly).
This implies that the session between the 2 systems is
held until SYNCPOINT is issued. It also means that the
server program cannot issue a SYNCPOINT request.
When SYNCONRETURN is specified, the server mirror
program will automatically issue a SYNCPOINT when the
server program RETURNs.This commits any updates in the
server system, and any systems to which the server has
initiated communication; the SYNCPOINT does NOT flow
back to the client transaction. With this option in
force, the server program is allowed to issue its own
explicit SYNCPOINTs, and the session is ended when the
server returns control to the client.
TRANSID(name) By default, the server program runs under the mirror
transaction code CPMI, although EIBTRNID contains the
name of the client transaction. When this option is
specified, this is the transaction code under which
the server will run. This means that the transaction
code must be defined in the server system's PCT, and
it must point to the mirror program (FAAMIR in CICS
OS/2, DFHMIRS in mainframe CICS systems). Note that
COMMAREA data will NOT be automatically converted
between ASCII and EBCDIC if this option is used; data
conversion is the responsibility of the user. This
value overrides any TRANSID specified in the PPT entry
for the program.
2
New/changed conditions may be raised in response to LINK -
INVREQ LENGERR ROLLEDBACK SYSIDERR TERMERR
Each of these can have different EIBRESP2 values; see the CICS/ESA 3.3 APR for
details.
Several commands are restricted when issued within a server environment,mostly
related to terminal handling. If a restricted command is issued, an INVREQ
condition will be raised, with EIBRESP2 set to 200; if the condition is not
catered for using HANDLE CONDITION or the NOHANDLE option, then the server
program will be abended ADPL (note, not AEIP). Restricted commands are -
ADDRESS TCTUA
ASSIGN terminal-related options
CONNECT PROCESS
CONVERSE
EXTRACT PROCESS
FREE
HANDLE AID
ISSUE ABEND/CONFIRMATION/ERROR/SIGNAL CONVID
RECEIVE
SEND
SIGNOFF
SIGNON
SYNCPOINT (ROLLBACK)
WAIT CONVID
The terminal I/O commands are not allowed to refer to the Principal Facility,
i.e. EIBTRMID, which is the LU6.2 session; it is in order for a server program
to, for example, initiate a DTP conversation with another system (or even back
to the client system, but this will require a separate session).
SYNCPOINT (ROLLBACK) is valid if SYNCONRETURN was specified on the LINK.
For further information, see the CICS/ESA 3.3 APR and APG manuals.
3
Changes due to fix for APAR PN27302
────────────────────────────────────
APAR PN27302 introduces changes to the processing of CVT conversion
templates. Please see the text of the APAR for full details.
4
**************************************************************
**************************************************************
*** ***
*** End of PTF 19 updates. ***
*** Updates for previous PTFs follow. ***
*** ***
**************************************************************
**************************************************************
i
README.TXT FOR
CICS OS/2 1.2.0 SERVICE LEVEL 18
17 August 1992
TABLE OF CONTENTS
─────────────────
Introduction . . . . . . . . . . . . . . . . . . . . . 1
Current Level . . . . . . . . . . . . . . . . . . . . . 1
Hints and other information. . . . . . . . . . . . . . 1
Supply of new ECI in PTF 18. . . . . . . . . . . . . 1
Supply of new File Manager in PTF18. . . . . . . . . 1
1
INTRODUCTION
────────────
CURRENT LEVEL
─────────────
The current level of CICS OS/2 is 1.2.0. Service Level 18.
HINTS AND OTHER INFORMATION.
────────────────────────────
SUPPLY OF NEW ECI VERSION IN PTF18
────────────────────────────────────
A new version of the Extended Call Interface (ECI) is
included in this PTF (PTF18) and fixes the problems reported
in APARs PN20922,PN21343 and PN25443. The File ECI.DOC contains
the information necessary to use this new version.
SUPPLY OF NEW FILE MANAGER IN PTF18
────────────────────────────────────
PTF 18 contains a new version of the CICS OS/2 File Manager which
provides improved performance and functionality. It also guarantees
full forward compatibility for all system and user files, however
after the upgrade has been performed the user may not revert to
the pre-PTF 18 version of the File Manager. Users should ensure
that adequate backups of their existing files are taken *before*
starting CICS with the new File Manager.
2
**************************************************************
**************************************************************
*** ***
*** End of PTF 18 updates. ***
*** Updates for previous PTFs follow. ***
*** ***
**************************************************************
**************************************************************
i
README.TXT FOR
CICS OS/2 1.2.0 SERVICE LEVEL 17
27 July 1992
TABLE OF CONTENTS
─────────────────
Introduction . . . . . . . . . . . . . . . . . . . . . 1
Current Level . . . . . . . . . . . . . . . . . . . . . 1
Hints and other information. . . . . . . . . . . . . . 1
Changes due to fix for APAR PN00194. . . . . . . . . 1
Changes due to fix for APAR PN19943. . . . . . . . . 3
1
INTRODUCTION
────────────
CURRENT LEVEL
─────────────
The current level of CICS OS/2 is 1.2.0. Service Level 17.
HINTS AND OTHER INFORMATION.
────────────────────────────
CHANGES DUE TO FIX FOR APAR PN00194.
────────────────────────────────────
This APAR introduces 'C' language sample programs.
INSTRUCTION FOR THE 'C' LANGUAGE SAMPLE TRANSACTIONS.
This PTF provides 'C' language sample transactions
equivalent to the COBOL language samples.
They are:
o FAACCALL.CCS - FILEA Add / Inquire / Update
o FAACCBRW.CCS - FILEA Browse
o FAACCCOM.CCS - FILEA Order Entry Queue Print
o FAACCMNU.CCS - FILEA Operator Instruction Menu
o FAACCREN.CCS - FILEA Order Entry
o FAACCREP.CCS - FILEA Low Balance Inquiry
plus the 'C' header files:
o FAACCL86.H
o FAACCFIL.H
and the corresponding BMS maps:
o FAACCMA.BMS
o FAACCMB.BMS
o FAACCMC.BMS
o FAACCMD.BMS
o FAACCMK.BMS
o FAACCML.BMS
2
Proceed as follows:
1. Run the BMS map translator against each of the map
files.
For example: CICSMAP FAACCMA
This will generate the maps themselves and produce the
the 'C' language header files FAACCG*.H.
3. Translate, compile and link each of the application pro-
grams remembering to specify the 'MAIN' option.
For example: CICSCTCL FAACCALL MAIN
If necessary (dependent on your setup) move the
FAACC*.DLL files into the CICS OS/2 execution directory
(normally CICS120\OS2DSD).
4. Bring up CICS OS/2 and define the following entries in
the PCT using CEDA:
a. PCT.
o CADD - FAACCALL
o CBRW - FAACCBRW
o CCOM - FAACCCOM
o CINQ - FAACCALL
o CMNU - FAACCMNU
o CORQ - FAACCCOM
o CREN - FAACCREN
o CREP - FAACCREP
o CUPD - FAACCALL
The detail of the PCT entry is the same as the for
the equivalent COBOL language entry.
5. Shut CICS OS/2 down using CQIT.
6. Bring up CICS OS/2 (to make the PCT & PPT entries
active).
3
To run the 'C' language Sample transactions proceed as with
the COBOL language Sample transactions but use the trans-
action names defined above. For example:
o to get the menu use 'CMNU'.
o on the menu panel use 'CBRW', 'CADD', 'CINQ' & 'CUPD'
instead of 'BRWS' 'ADDS' 'INQY' & 'UPDT' to Browse / Add
/ Inquire / Update records on FILEA.
o to run Order Entry use 'CREN'.
o to run Order Entry Queue Print use 'CCOM'.
o to run Low Balance Inquiry use 'CREP'.
CHANGES DUE TO FIX FOR APAR PN19943.
────────────────────────────────────
The CICS OS/2 Translator now only processes valid COBOL STOP
statements i.e. 'STOP RUN' or 'STOP nn' where 'nn' is an
integer value. The word single word 'STOP' will no longer be
commented out by the translator.
4
**************************************************************
**************************************************************
*** ***
*** End of PTF 17 updates. ***
*** Updates for previous PTFs follow. ***
*** ***
**************************************************************
**************************************************************
i
README.TXT FOR
CICS OS/2 1.2.0 SERVICE LEVEL 16
12 June 1992
TABLE OF CONTENTS
─────────────────
Introduction . . . . . . . . . . . . . . . . . . . . . 1
Current Level . . . . . . . . . . . . . . . . . . . . . 1
Hints and other information. . . . . . . . . . . . . . 1
Changes due to fix for APAR PN20903. . . . . . . . . 1
Changes due to fix for APAR PN22292. . . . . . . . . 2
1
INTRODUCTION
────────────
CURRENT LEVEL
─────────────
The current level of CICS OS/2 is 1.2.0. Service Level 16.
HINTS AND OTHER INFORMATION.
────────────────────────────
CHANGES DUE TO FIX FOR APAR PN20903.
────────────────────────────────────
The following trace points were introduced / changed:
┌────────────────────────────────────────────────────────────────────┐
│ ID = 01 Issued by FAASRSML OS/2 Server mainline │
├─────────┬──────────────────────┬─────────────────┬─────────────────┤
│ TYPE / │ ENTRY DESCRIPTION │ FIELD A │ FIELD B │
│ POINT │ │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SV M80 │ Generate ICE Entry │ 2byte Rec. count│ DCT queue status│
│ │ - check. │ 2byte Low-values│ 1byte low-value │
│ │ │ │ DCT ATI status │
│ │ │ │ 1byte low-value │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SV M76 │ Generate ICE Entry │ 4byte Transid │ DCT queue status│
│ │ - entry. │ │ 1byte low-value │
│ │ │ │ DCT ATI status │
│ │ │ │ 1byte low-value │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SV M81 │ Generate ICE Entry │ 2byte Retn. code│ DCT queue status│
│ │ - result. │ 2byte Low-values│ 1byte low-value │
│ │ │ │ DCT ATI status │
│ │ │ │ 1byte low-value │
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
┌────────────────────────────────────────────────────────────────────┐
│ ID = 56 Issued by FAAOTPTK OS/2 task control │
├─────────┬──────────────────────┬─────────────────┬─────────────────┤
│ TYPE / │ ENTRY DESCRIPTION │ FIELD A │ FIELD B │
│ POINT │ │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SV K91 │ DCT Entry status │ 2byte Retn. code│ DCT queue status│
│ │ │ 2byte DCT index │ 1byte low-value │
│ │ │ │ DCT ATI status │
│ │ │ │ 1byte low-value │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SV K92 │ DCT Queue status │ 2byte Retn. code│ DCT queue status│
│ │ │ 2byte DCT index │ 1byte low-value │
│ │ │ │ DCT ATI status │
│ │ │ │ 1byte low-value │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SV K93 │ DCT Queue status │ 2byte Start-code│ DCT queue status│
│ │ │ 2byte DCT index │ 1byte low-value │
│ │ │ │ DCT ATI status │
│ │ │ │ Facility type │
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
2
┌────────────────────────────────────────────────────────────────────┐
│ ID = 01 Issued by FAASRCTS OS/2 Server TD and TS │
├─────────┬──────────────────────┬─────────────────┬─────────────────┤
│ TYPE / │ ENTRY DESCRIPTION │ FIELD A │ FIELD B │
│ POINT │ │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ │ │ │ │
│ SV T17 │TD Lock queue entry │ 4byte Q. handle │ Dest-id │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SV T18 │TD Lock Q. semaphore│ 2byte Retn. code│ Low-values │
│ │ │ 2byte Low-values│ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SV T19 │TD Lock queue exit │ 2byte Retn. code│ 2byte Retn. code│
│ │ │ 2byte Retn. code│ 2byte Low-values│
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
CHANGES DUE TO FIX FOR APAR PN22292.
────────────────────────────────────
The CICS OS/2 trace taken from a system running on OS/2 (not DOS)
will now indicate the Service level (PTF level) of the CICS system.
The following trace point was changed:
┌────────────────────────────────────────────────────────────────────┐
│ ID = 42 Issued by FAAOMPTR OS/2 trace monitor │
├─────────┬──────────────────────┬─────────────────┬─────────────────┤
│ TYPE / │ ENTRY DESCRIPTION │ FIELD A │ FIELD B │
│ POINT │ │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ │ │ │ │
│ TV T09 │Trace block released │ Bytes 1 - 4 of │ Bytes 5-6 of TOD│
│ │ │time-of-day (TOD)│ 2byte PTF Level │
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
3
**************************************************************
**************************************************************
*** ***
*** End of PTF 16 updates. ***
*** Updates for previous PTFs follow. ***
*** ***
**************************************************************
**************************************************************
i
README.TXT FOR
CICS OS/2 1.2.0 SERVICE LEVEL 15
21 May 1992
TABLE OF CONTENTS
─────────────────
Introduction . . . . . . . . . . . . . . . . . . . . . 1
Current Level . . . . . . . . . . . . . . . . . . . . . 1
Hints and other information. . . . . . . . . . . . . . 1
Changes due to fix for APAR PN04245. . . . . . . . . 1
Changes due to fix for APAR PN12497. . . . . . . . . 1
Changes due to fix for APAR PN13710. . . . . . . . . 1
1
INTRODUCTION
────────────
CURRENT LEVEL
─────────────
The current level of CICS OS/2 is 1.2.0. Service Level 15.
HINTS AND OTHER INFORMATION.
────────────────────────────
CHANGES DUE TO FIX FOR APAR PN04245.
────────────────────────────────────
The CICS OS/2 COBOL Translator has been changed. If a $SET
statement is encountered during translation it is inserted into
the .CBL file before a comment line is inserted to show date
and time.
CHANGES DUE TO FIX FOR APAR PN12497.
────────────────────────────────────
The CICS OS/2 Translator has been changed to process the
EXEC CICS SEND MAP command correctly. The LENGTH option
is no longer required.
CHANGES DUE TO FIX FOR APAR PN13710.
────────────────────────────────────
The CICS OS/2 Translator has been changed to process the
EXEC CICS RECEIVE INTO(....) command correctly. The LENGTH
option is no longer required.
**************************************************************
**************************************************************
*** ***
*** End of PTF 15 updates. ***
*** Updates for previous PTFs follow. ***
*** ***
**************************************************************
**************************************************************
i
README.TXT FOR
CICS OS/2 1.2.0 SERVICE LEVEL 14
30 Apr 1992
TABLE OF CONTENTS
─────────────────
Introduction . . . . . . . . . . . . . . . . . . . . . 1
Current Level . . . . . . . . . . . . . . . . . . . . . 1
Hints and other information. . . . . . . . . . . . . . 1
Changes due to fix for APAR PN11097. . . . . . . . . 1
Changes due to fix for APAR PN13285. . . . . . . . . 1
Changes due to fix for APAR PN00015. . . . . . . . . 3
Changes due to fix for APAR PN07068. . . . . . . . . 3
1
INTRODUCTION
────────────
CURRENT LEVEL
─────────────
The current level of CICS OS/2 is 1.2.0. Service Level 14.
HINTS AND OTHER INFORMATION.
────────────────────────────
CHANGES DUE TO FIX FOR APAR PN11097.
────────────────────────────────────
A new help panel FAAED1 which consists of 2 pages has been
introduced to explain transaction CADL and its various
options.
CHANGES DUE TO FIX FOR APAR PN13285.
────────────────────────────────────
PN13285 fixes the following translator problems -
1. OLDCOPY processing now works correctly, including nested
COPY statements.
2. COPY statements which are commented out by means of '*'
in column 1 are ignored (this applies to all lines which
begin '*' in column 1).
3. A new translator directive is introduced -
(NO)PROCESSCOPY. This is used to specify whether COPY
statements are processed by the CICS OS/2 translator or
passed through to the COBOL Compiler. N.B. The default
is PROCESSCOPY, i.e. COPY statements will be processed
by the translator.
NOPROCESSCOPY should not be specified in the following
cases -
∙ Code copied into the Linkage Section contains an
01-level definition
which is referred to by a SERVICE RELOAD statement.
∙ Code copied into the Procedure Division contains
EXEC CICS commands .
∙ code copied into WORKING STORAGE section also
contains LINKAGE SECTION and or
PROCEDURE DIVISION STATEMENTS
Example CCP Program using OLDCOPY:-
2
CBL XOPTS(PROCESSCOPY OLDCOPY).
IDENTIFICATION DIVISION.
PROGRAM-ID. 1x310.
ENVIRONMENT DIVISION.
DATA DIVISION.
WORKING-STORAGE SECTION.
01 DATA-AREA COPY OLD1X310.
PROCEDURE DIVISION.
EXEC CICS RETURN END-EXEC.
Example Copybook:-
01 OLD-AREA.
05 FILLER PIC X(80).
3
CHANGES DUE TO FIX FOR APAR PN00015.
────────────────────────────────────
The following trace points were introduced / changed:
┌────────────────────────────────────────────────────────────────────┐
│ ID = 01 Issued by FAASRSML OS/2 Server mainline │
├─────────┬──────────────────────┬─────────────────┬─────────────────┤
│ TYPE / │ ENTRY DESCRIPTION │ FIELD A │ FIELD B │
│ POINT │ │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ │ │ │ │
│ SN M70 │Enter Rollback TD │ Low-values │ Low-values │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M71 │Exit Rollback TD │ 2byte Retn-code │ Low-values │
│ │ │ 2byte Low-values│ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M72 │TD Commit - Phase 1 │ Low-values │ Low-values │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M73 │TD Commit - Phase 1 │ 2byte Retn-code │ 2byte Xact count│
│ │ │ 2byte Retn-code │ 2byte Low-values│
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M74 │TD Commit - Phase 2 │ Low-values │ Low-values │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M75 │TD Commit - Phase 2 │ 2byte Retn-code │ Low values │
│ │ │ 2byte Low-values│ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M76 │Generate ICE Entry │ Low-values │ TransId │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M77 │Generate ICE Entry │ 2byte Retn-code│ Destination │
│ │ │ 2byte Low-values│ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN M78 │TD purge queue │ Destination name│ Low-values │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX M79 │TD purge queue │ 2byte Retn-code │ Queue name │
│ │ │ 2byte Low-values│ │
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
4
┌────────────────────────────────────────────────────────────────────┐
│ ID = 01 Issued by FAASRCTS Server TD/TS │
├─────────┬──────────────────────┬─────────────────┬─────────────────┤
│ TYPE / │ ENTRY DESCRIPTION │ FIELD A │ FIELD B │
│ POINT │ │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ │ │ │ │
│ SX T04 │After TS Get Last │ 2byte Retn-code │Record-key │
│ │ │ 2byte Rec-key │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN T10 │Lock TD Write │ Handle │Dest name │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SE T11 │TD Write SemRequest │ 2byte Retn-code │Low-values │
│ │ │ 2byte Low-values│ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX T12 │TD Write SemRequest │ 2byte Retn-code │ 2byte Pid │
│ │ │ 2byte Low-values│ 2byte Low-values│
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SN T13 │Lock TD Read │ Handle │ Dest name │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SE T14 │TD Read SemRequest │ 2byte Retn-code │ Low-values │
│ │ │ 2byte Low-values│ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ SX T12 │TD Read SemRequest │ 2byte Retn-code │ 2byte Pid │
│ │ │ 2byte Low-values│ 2byte Low-values│
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
CHANGES DUE TO FIX FOR APAR PN07068.
────────────────────────────────────
The CICS OS/2 COBOL Translator has been changed to search
for copybooks with no file extension or a file extension of
.CPY, in addition to .CBL. It is no longer necessary to use
a file extension of .CBL for files referenced in COPY
commands in a COBOL program.
**************************************************************
**************************************************************
*** ***
*** End of PTF 14 updates. ***
*** Updates for previous PTFs follow. ***
*** ***
**************************************************************
**************************************************************
i
README.TXT FOR
CICS OS/2 1.20 SERVICE LEVEL 13
31 MARCH 1992
TABLE OF CONTENTS
_________________
Current Level . . . . . . . . . . . . . . . . . . . . . 1
Hints and other information. . . . . . . . . . . . . . 1
Changes due to fix for APAR PL76806 . . . . . . . . . 1
Changes due to fix for APAR PN16425 . . . . . . . . . 1
1
CURRENT LEVEL
_____________
The current level of CICS OS/2 is 1.20. Service Level 13.
HINTS AND OTHER INFORMATION.
____________________________
CHANGES DUE TO FIX FOR APAR PL76806
A new version of the Extended Call Interface (ECI) is
included in this PTF (PTF13) and fixes the problem reported
in APAR PL76806. File ECI.DOC contains the information
necessary to use this new version.
CHANGES DUE TO FIX FOR APAR PN16425
If you require the fix detailed in the above APAR, then all
affected applications must be re-translated and compiled as
the fix is implemented in the CICS OS/2 COBOL Translator.
**************************************************************
**************************************************************
*** ***
*** End of PTF 13 updates. ***
*** Updates for previous PTFs follow. ***
*** ***
**************************************************************
**************************************************************
i
README.TXT FOR
CICS OS/2 1.2.0 SERVICE LEVEL 12
3 Mar 1992
TABLE OF CONTENTS
_________________
Introduction . . . . . . . . . . . . . . . . . . . . . 1
Current Level . . . . . . . . . . . . . . . . . . . . . 1
Hints and other information. . . . . . . . . . . . . . 1
Changes due to fix for APAR PN06725. . . . . . . . . 1
Changes due to fix for APAR PN06573. . . . . . . . . 2
Changes due to fix for APAR PN09479. . . . . . . . . 2
Changes due to fix for APAR PN10386. . . . . . . . . 2
Changes due to fix for APAR PN11715. . . . . . . . . 3
Changes due to fix for APAR PN12231. . . . . . . . . 3
1
INTRODUCTION
____________
CURRENT LEVEL
_____________
The current level of CICS OS/2 is 1.2.0. Service Level 12.
HINTS AND OTHER INFORMATION.
____________________________
CHANGES DUE TO FIX FOR APAR PN06725.
PN06725 changes the operation of the CICS OS/2 map
translator as follows :-
1. The length of INITIAL data is checked against the value
given for LENGTH for non-named fields - it already does
the check for named fields.
2. In INITIAL data to obtain the character '&' (ampersand)
the character '&&' (two ampersands) must be used. This
is to maintain compatibility with the host map
translator.
3. A new message - 'FAA1900W Unmatched open or close
brackets on %1' - has been added. This will be issued
if there are missing opening '(' or closing ')' brackets
detected while checking the map source.
2
CHANGES DUE TO FIX FOR APAR PN06573.
The following duplicate trace points have been changed.
∙ 50R02 is now 50R22 Sect Error.
Field A: HUD Xmit sequence number.
Field B: HUD Receive sequence number.
∙ 50R10 is now 50R30 Routine Error.
Field A: HUD Header byte 9.
Field B: Return code.
CHANGES DUE TO FIX FOR APAR PN09479.
PN09479 changes the CICS OS/2 COBOL translator to accept an
'*' (asterisk) in column 1 of a record in the source file
and treat that record as a comment. The record will
subsequently be treated as a comment by the COBOL compiler.
CHANGES DUE TO FIX FOR APAR PN10386.
PN10386 has added the following new trace points.
∙ Major Event. 62T10. Remote Logon Details.
Field A : USERID
Field B : password
∙ Major Event. 62T11. Local Authorisation Details.
Field A : 'LOCL'
Field B : (1:1) Local sign-on flag
(3:1) Authorisation flag
3
CHANGES DUE TO FIX FOR APAR PN11715.
PN11715 makes the following changes to trace.
Tracepoint 01I04 has been modified to trace EIB-CC in field
A and the Return Code in field B.
∙ Exit from Section. 01I04. Exit from Delay Post.
Field A : EIB-CC
Field B : Return Code
Tracepoint 01I09 has been added trace DosCreateSem errors
where field A contains the Return Code and field B the
semaphore handle returned by OS/2.
∙ Basic Error. 01I09. DosCreateSem errors.
Field A : Return Code
Field B : Semaphore Handle returned by OS/2
CHANGES DUE TO FIX FOR APAR PN12231.
PN12231 corrects 3270 screen colours to match those of the
host. As a result, some BMS maps may change after the
application of this PTF.
**************************************************************
**************************************************************
*** ***
*** End of PTF 12 updates. ***
*** Updates for previous PTFs follow. ***
*** ***
**************************************************************
**************************************************************
i
README.TXT FOR
CICS OS/2 1.2.0 SERVICE LEVEL 11
08 Nov 1991
TABLE OF CONTENTS
_________________
Introduction . . . . . . . . . . . . . . . . . . . . . 1
Current Level . . . . . . . . . . . . . . . . . . . . . 1
iiAPAR Information . . . . . . . . . . . . . . . . . . 1
Preventative Maintenance . . . . . . . . . . . . . . 1
Hints and other information. . . . . . . . . . . . . . 1
Changes due to fix for APAR PN01818. . . . . . . . . 1
Changes due to fix for APAR PL80856. . . . . . . . . 2
Changes due to fix for APAR PL84380. . . . . . . . . 2
Changes due to fixes for APAR PN02394 and PN02488. . 2
COMMAREA Changes. . . . . . . . . . . . . . . . . . . 2
1
INTRODUCTION
____________
CURRENT LEVEL
_____________
The current level of CICS OS/2 is 1.2.0. Service Level 11.
IIAPAR INFORMATION
__________________
The following is from information APAR No. II05130:
( The RETAIN version of II05130 may contain more recent
information.)
PREVENTATIVE MAINTENANCE
Preventative maintenance for CICS OS/2 is available in SMP/E
and MSHP format only. Preventative maintenance will be
shipped under an accumulative PTF containing multiple APAR
fixes. This will be known as a Service Level or PTF level.
When available, corrective service for individual APAR fixes
will be shipped by the change team to individual Customers
as needed on diskette.
Following is a cross reference list of Service Levels for
MVS and VSE PTF numbers:
----------------------------------------------------------------
SERVICE/PTF P T F N U M B E R S
LEVEL MVS VSE
================================================================
4 UL85512 UL85513
5 UL89760 UL89761
6 UL95379 UL95380
7 UL97427 UL97434
8 UN03147 UN03148
9 UN05594 UN05595
10 UN08283 UN08284
================================================================
PTF LEVEL 8 IS THE MINIMUM RECOMMENDED LEVEL TO RUN CICS OS/2.
================================================================
2
HINTS AND OTHER INFORMATION.
____________________________
CHANGES DUE TO FIX FOR APAR PN01818.
PN01818 has changed the way that inter-system communication
sessions are handled internally. Sessions are no longer
reserved as Receive or Send sessions, but are pooled to be
used for send or receive as required.
The CEDA TCS definition screen is not, however, updated with
this APAR, so no changes to existing system definitions are
required. For each system defined, the numbers of Send and
Receive sessions specified are added to give the session
pool size. Session ids are now generated internally, and
the Send and Receive prefixes are ignored.
CHANGES DUE TO FIX FOR APAR PL80856.
If when CICS OS/2 is coming up it fails to open a file,
error message FAA1672S is issued. The fix for this APAR has
made sure that the path for the file is searched backwards
and just the filename.extension passed to the error message.
This will avoid ambiguous file names being issued by the
FAA1672S error message.
CHANGES DUE TO FIX FOR APAR PL84380.
This fix has addressed the area of bringing up a CICS OS/2
system with a large number of tasks. It is recommended
however that the highest number of free tasks specified be
set to no greater than 30. Please note that this will have
an impact on system performance and is configuration
dependant.
CHANGES DUE TO FIXES FOR APAR PN02394 AND PN02488.
If you require the fixes detailed in the above APAR's,
affected transactions will need to be re-translated and
compiled as the fixes are implemented in the CICS OS/2
translator.
COMMAREA CHANGES.
The process of COMMAREA checking has been amended to ensure
that more complete checking is done. If using the COMMAREA
the user must ensure that the length specified in EIBCALEN
is used. If this is not done and a length greater than that
specified in EIBCALEN is used a TRAP 000D is issued.
**************************************************************
**************************************************************
*** ***
*** End of PTF 11 updates. ***
*** Updates for previous PTFs follow. ***
*** ***
**************************************************************
**************************************************************
i
README.TXT FOR
CICS OS/2 1.2.0 SERVICE LEVEL 10
11 Sept 1991
TABLE OF CONTENTS
_________________
Introduction . . . . . . . . . . . . . . . . . . . . . 1
Current Level . . . . . . . . . . . . . . . . . . . . . 1
iiAPAR Information . . . . . . . . . . . . . . . . . . 1
Preventative Maintenance . . . . . . . . . . . . . . 1
Hints and other information. . . . . . . . . . . . . . 2
CICS OS/2 and ANIMATOR . . . . . . . . . . . . . . . 2
Use of CICSRGRP. . . . . . . . . . . . . . . . . . . 3
ECI Sample Programs. . . . . . . . . . . . . . . . . 3
1
INTRODUCTION
____________
The README TXT file was NOT updated with PTF 09 (Service
Level 09).
CURRENT LEVEL
_____________
The current level of CICS OS/2 is 1.2.0. Service Level 10.
IIAPAR INFORMATION
__________________
The following is from information APAR No. II05130:
PREVENTATIVE MAINTENANCE
Preventative maintenance for CICS OS/2 is available in SMP/E
and MSHP format only. Preventative maintenance will be
shipped under an accumulative PTF containing multiple APAR
fixes. This will be known as a Service Level or PTF level.
When available, corrective service for individual APAR fixes
will be shipped by the change team to individual Customers
as needed on diskette.
Following is a cross reference list of Service Levels for
MVS and VSE PTF numbers:
----------------------------------------------------------------
SERVICE/PTF P T F N U M B E R S
LEVEL MVS VSE
================================================================
4 UL85512 UL85513
5 UL89760 UL89761
6 UL95379 UL95380
7 UL97427 UL97434
8 UN03147 UN03148
9 UN05594 UN05595
10 PTF NOT ASSIGNED PTF NOT ASSIGNED
================================================================
PTF LEVEL 4 IS THE MINIMUM RECOMMENDED LEVEL TO RUN CICS OS/2.
================================================================
2
HINTS AND OTHER INFORMATION.
____________________________
CICS OS/2 AND ANIMATOR
The Systems and Application Guide states:
"When you compile a program with ANIMATOR or Advanced
ANIMATOR, files with suffixes .IDY and .INT are produced.
ANIMATOR or Advanced ANIMATOR must use these files when
stepping through the program. Always delete or rename the
.DLL file before running either of these debugging tools, to
prevent it from picking up the wrong file".
The above is only true if you are using the MicroFocus
Programmer's Workbench.
ANIMATOR support for CICS OS/2 is also available if you
only have the MicroFocus COBOL/2 compiler, however, unlike
the Workbench the compiler does not contain a COBOL runtime
system therefore some changes have to be made.
The following should be carried out to enable CICS OS/2
transactions to be animated when only the compiler is being
used:
1. Translate the CICS program in the usual way (CICSTRAN)
2. Compile the program with the /ANIM option and also the
OPT"0" option (if OPT"0" is not specified the linker is
implicitly invoked and an attempt to find a library
called OS2.LIB will fail).
3. Link the program in the usual way using CICSLINK
(FAACLIB, DOSCALLS and COBLIB).
A IDY and a .DLL file will be produced. No INT file will be
produced.
Both the .IDY file AND the .DLL file must be available to
run this program under ANIMATOR on a CICS DEBUG screen. The
.DLL file will also run on a normal non-animated terminal.
3
USE OF CICSRGRP.
When CICS is initialised it is important to understand how
control table entries are loaded.
∙ SIT - The last entry is always used regardless of the
number of
entries specified.
∙ ALL OTHERS - If CICSRGRP is not specified and an entry
exists in
more than one group the alphabetically highest is
loaded.
If CICSRGRP is specified the groups are loaded
alphabetically,
regardless of the order in which they were
specified. If
an entry exists in more than one of the specified
groups the
alphabetically higher is loaded.
ECI SAMPLE PROGRAMS.
The ECI sample programs FAADECIC.CCS and FAAECIP.C as
described in the CICS OS/2 System and Application Guide,
(SC33-0616-3), page 334, are being shipped in PTF10.
Please note that in the CICS OS/2 Systems and Application
Guide (SC33-0616-3), page 334. The paragraph reading :-
The sample C language program is not listed in this book.
It is provided in the program FAADECIC.CCS. This calls the
OS/2 program FAAECIP.C, which is also provided.
Should read :-
The sample C language program is not listed in this book.
It is provided in the program FAADECIC.CCS. This is invoked
by the OS/2 program FAAECIP.C, which is also provided.
**************************************************************
**************************************************************
*** ***
*** End of PTF 10 updates. ***
*** Updates for previous PTFs follow. ***
*** ***
**************************************************************
**************************************************************
i
README.TXT FOR
CICS OS/2 1.2.0 SERVICE LEVEL 8
18 July 1991
TABLE OF CONTENTS
_________________
Introduction . . . . . . . . . . . . . . . . . . . . . 1
Current Level . . . . . . . . . . . . . . . . . . . . . 1
iiAPAR Information . . . . . . . . . . . . . . . . . . 1
PROBLEMS while Deleting CVT entries using CEDA . . . 1
Using User Trace Points to trace Application Program
Flow . . . . . . . . . . . . . . . . . . . . . . . . 2
GDDM not Supported by CICS OS/2 . . . . . . . . . . . 2
New Information APAR . . . . . . . . . . . . . . . . 2
Hints and other information. . . . . . . . . . . . . . 3
Changes due to fix for APAR PL70072 . . . . . . . . . 3
Communications Setup . . . . . . . . . . . . . . . . 3
Information on User Exits 01 and 11 . . . . . . . . . 4
Additional Trace Point Information due to fix for APAR
PL70085 . . . . . . . . . . . . . . . . . . . . . . 6
Information for WSU on a 3151/61 U.S Keyboard . . . . 6
1
INTRODUCTION
____________
This README contains information on:
changes due to fix for APAR PL70072;
a new CICSCFG.INF file for assisting with Communications
Setup;
additional trace point information due to fix for APAR
PL70085;
plus the information from the latest information APAR.
CURRENT LEVEL
_____________
The current level of CICS OS/2 is 1.2.0. Service Level 8.
IIAPAR INFORMATION
__________________
The following is the latest from information APAR No.
ii04935:
PROBLEMS WHILE DELETING CVT ENTRIES USING CEDA
1. Adding a key type (K) sequence number table entry can be
done as normal
a. The message "FAA4818I RECORD ADDED SUCCESSFULLY.
PRESS ENTER." appears.
Pressing <ENTER> key will produce a message
"FAA4821E INCONSISTENT TABLE UPDATE"
Pressing <F3> key will return the user to the
previous level of menu without error.
b. The new table entry will not, however, be
displayed!!
c. By pressing <F3> again to return to the main CEDA
menu and then re-selecting the "CVT" option the new
entry will be visible.
2. Deleting a key type (K) sequence number table entry can
be done as follows:
a. Select the item to be deleted using the "/"
character and press <F10> to activate the option bar
at the top of screen
2
b. Select the update option. (YES UPDATE AND NOT
DELETE!!)
c. When the table entry is displayed for updating
Set "NO. OF TEMPLATE ENTRIES " to '0' (ZERO)
Erase all "TYPE", "OFFSET" AND "LENGTH" fields
to (BLANKS)
d. Press <ENTER> key to perform changes.
e. Message "FAA4819I RECORD UPDATED SUCCESSFULLY. PRESS
ENTER..." is displayed on the screen.
If the <ENTER> key is pressed message "FAA4821E
INCONSISTENT TABLE UPDATE" is displayed.
If however <F3> is displayed the user returns
successfully to previous level of menu.
f. The table entry should have been deleted OK.
USING USER TRACE POINTS TO TRACE APPLICATION PROGRAM FLOW
It is possible to use the CICS OS/2 trace CTRA to trace user
trace points in an application to assist de-bugging. This
is done by placing:
EXEC CICS ENTER TRACEID(nnn) FROM(aaaabbbb)
statements in the user application. These trace points can
then be seen in the trace file FAATAFEN.TRC as follows:
MAJ. ENTRY 01M01 0072 0000 <--- ENTER stmt
BASIC EVENT 01M21 F T <--- FROM & TRACEID
BASIC EVENT 01M22
MAJ. EVENT UFnnn aaaa bbbb <-- User data
MAJ. EXIT 01M06 .... ....
If the RESOURCE option is used on the ENTER statement the
trace point is 'UR'
GDDM NOT SUPPORTED BY CICS OS/2
It should be noted that although host CICS supports
transactions containing GDDM calls - CICS OS/2 does NOT
support the level of data stream required by GDDM therefore
it is not possible to transaction route from CICS OS/2 to
host CICS - run a GDDM transaction - and then have the
output displayed back on the CICS OS/2 PWS.
NEW INFORMATION APAR
Information APARs will be entered on RETAIN as and when
required.
3
HINTS AND OTHER INFORMATION.
____________________________
CHANGES DUE TO FIX FOR APAR PL70072
APAR PL70072 rationalises the data written to transient data
(TD) queue 'CSCS' by transactions 'CESN' and 'CSSF' and adds
the terminal ID to this data.
The format of the data written is:
1. Transaction ID - 12 characters
2. User ID - 8 characters
3. Terminal ID - 4 characters
4. System ID - 4 characters - For LU TYPE 2 connections.
5. Date - 00YYDDD+ (packed decimal EIB format)
6. Time - 0HHMMSS+ (packed decimal EIB format)
The transaction ID will be:
'CESN '
'CSSF '
'CSSF LOGOFF '
COMMUNICATIONS SETUP
A file is provided, CICSCFG.INF, in the OS2DSD sub-directory
that provides information about setting up CICS OS/2
communications for both APPC and NetBIOS.
This file is in OS/2 IPF format and can be viewed on OS/2 EE
1.2 or later by using the OS/2 VIEW command.
E.G
VIEW CICSCFG
4
Information on User Exits 01 and 11. Program FAAEXP01.
-----------------------------------------------------------
This sample exit module is distributed with CICS OS/2, and
provides a mechanism to modify the terminal name as seen by
a remote CICS system.
The sample as distributed with the base CICS OS/2 System,
Version 1.2, only supported outbound operations and was
invoked by Exit 01. The sample used the first character of
the local terminal name and the last three characters of the
connection netname to form a new terminal name for the
remote system. The CICS OS/2 terminal name remained
unchanged.
With Service Level 8 the terminal renaming function has been
extended to support both outbound and inbound operations.
The exit is called on outbound operations, as EXIT 01, and
modifies the terminal name as seen by the remote system. It
is also called on inbound operations as EXIT 11. EXIT 11
must be able to reverse the work performed in EXIT 01.
EXIT 01.
This exit is called for both function shipping and
transaction routing outbound. The supplied sample code will
only change the outbound name if the last three characters
of the name are '123' as in 'V123'.
EXIT 11.
This exit is called by the mirror transaction (CPMI or CVMI)
and by the service transaction CRSR. The supplied sample
code will, in this case, force the last three characters of
the inbound terminal name to '123', if the last three
characters of the inbound target terminal name are the same
as the last three characters of the connection netname.
This will complete the round trip for an aliased terminal
name.
An example.
Consider an EXEC CICS START command, with data, to terminal
V123 for a transaction defined on a remote system with a
connection netname of SYSXYZ. This will invoke three
distinct steps.
Step 1 will function ship the Start request to SYSXYZ
calling EXIT 01. EXIT 01, in this example, will change the
terminal ID from V123 to VXYZ and the start will be
scheduled on the remote system.
5
Step 2 occurs when the start time is reached. The
transaction CRSR ships the AID (Automatic Initiate
Descriptor) to the local system to start the original
transaction on terminal VXYZ. EXIT 11 is called and it
modifies the terminal ID back to V123 so that it can be
attached locally.
Step 3 is invoked when the transaction route is actually
started locally for V123. EXIT 01 is called and modifies
the outbound name back to VXYZ. When the remote system
attaches the transaction to the remote entry for VXYZ it
associates the original data that was function shipped and
the transaction runs normally.
Note in this sample EXIT the distributed local terminal id
V124 will not be changed either inbound or outbound. If it
is used for communicating with other CICS systems it must
therefore be unique, network wide, for all involved systems.
A user exit could generate a unique alias name for any local
terminal id involved with remote communications.
Additional Considerations.
Caution should be exercised in designing this exit program.
On the outbound side it requires to be able to distinguish
between terminals that must be aliased and those that
probably should not be alaised. Terminal definitions that
are shipped into the local environment probably should not
be alaised. This would be the case if during problem
determination a host terminal definition was shipped to the
local system in support of a CRTE session. On the inbound
side EXIT 11 must recognise the names that EXIT 01 has
shipped to remote systems and be able to convert them back
to the correct local name. Existing network naming
standards and the name space constraints of four characters
will dictate the best way to handle this EXIT set.
One alternative is to not use the EXIT 01/11 set, and to
have all terminal names unique within the CICS network.
6
ADDITIONAL TRACE POINT INFORMATION DUE TO FIX FOR APAR
PL70085
Trace Point : 35T11
Data output : Parameter1 - All zeroes
Parameter2 - All zeroes
Purpose : Enter 3270 Initialise Screen
Type :
Trace Point : 35T21
Data output : Parameter1 - display height 4 bytes hex
Parameter2 - display width 4 bytes hex
Purpose : Create Presentation Space
Type :
Trace Point : 35T22
Data output : Parameter1 - format id 4 bytes hex
Parameter2 - display attributes 4 bytes hex
Purpose : Create Presentation Space - cont.
Type :
Trace Point : 35T23
Data output : Parameter1 - code page 4 bytes hex
Parameter2 - All zeroes
Purpose : Specify Code Page.
Type :
Trace Point : 35T24
Data output : Parameter1 - Cell_Size.x 2 bytes hex
Cell_Size.y 2 bytes hex
Parameter2 - All zeroes
Purpose : Device Cell Size.
Type :
Trace Point : 35T13
Data output : Parameter1 - Return Code
Parameter2 - All zeroes
Purpose : Exit 3270 Initialise Screen.
Type :
INFORMATION FOR WSU ON A U.S 3151/61 KEYBOARD.
In order to use the keyboard sequence 'CTRL' & numeric keypad
'+' on a U.S 3151/61 keyboard under Work Station set Up (WSU),
the following must be performed:
Change the 'Break Signal' field on the Communications page of
the 3151 setup to 'DISABLE'.
This only applys to U.S 3151/61 keyboards when the 'CTRL' & '+'
is defined under CICS OS/2 Work Station set Up.
**************************************************************
**************************************************************
*** ***
*** End of PTF 8 updates. ***
*** Updates for previous PTFs follow. ***
*** ***
**************************************************************
**************************************************************
i
README.TXT FOR
CICS OS/2 1.2.0 SERVICE LEVEL 7
17 April 1991
TABLE OF CONTENTS
_________________
Introduction . . . . . . . . . . . . . . . . . . . . . 1
Current Level . . . . . . . . . . . . . . . . . . . . . 1
iiAPAR Information . . . . . . . . . . . . . . . . . . 1
NetBios and CICS OS/2 Performance Problems . . . . . 1
Use of CICSRGRP . . . . . . . . . . . . . . . . . . . 1
New Information APAR . . . . . . . . . . . . . . . . 2
Hints and other information. . . . . . . . . . . . . . 2
1
INTRODUCTION
____________
This README contains information from the latest information
APAR.
CURRENT LEVEL
_____________
The current level of CICS OS/2 is 1.2.0. Service Level 7.
IIAPAR INFORMATION
__________________
The following is the latest from information APAR No.
ii04748:
NETBIOS AND CICS OS/2 PERFORMANCE PROBLEMS
Users of CICS OS/2 communicating over token ring with
NetBios may experience performance problems. the problem is
known.
The solution is to install OS/2 1.2 CSD 4098 or OS/2 1.3.
USE OF CICSRGRP
When CICS OS/2 is initialised, if a control table entry
exists in more than one group, the alphabetically higher
entry is always used. This may cause confusion when using
CICSRGRP to control loading of tables. If an entry is in two
groups and both groups are selected, the last entry in the
control file is always loaded, regardless of the group order
in CICSRGRP.
For example:
FAACTFTB PCT entries:
Trans Group Sysid
----- ------ -----
MENU REMOTE SYSR
MENU FAAIVP
If CICS OS/2 is loaded without CICSGRP set, MENU is loaded
from group FAAIVP.
If CICS OS/2 is loaded with CICSRGRP set to
FAASYS,...,FAAIVP,REMOTE, MENU is still loaded from FAAIVP.
The only way to load MENU from the REMOTE group is to remove
FAAIVP from to CICSRGRP list.
Note. The SAG indicates that a message is issued if it finds
an entry in more than one group, this is NOT true.
2
NEW INFORMATION APAR
The new information APAR is ii04935
HINTS AND OTHER INFORMATION.
____________________________
EXTRA TRACE POINTS
The trace points listed below are new with APAR
PL77762
┌─────────┬────────────┬─────────────────────────────────────────────┐
│ TRACE │ MODULE │ MODULE DESCRIPTION │
│ ID │ NAME │ │
│ 01 │ FAASRSML │ Server mainline │
├─────────┼────────────┴─────────┬─────────────────┬─────────────────┤
│ TYPE │ ENTRY DESCRIPTION │ FIELD A │ FIELD B │
│ POINT │ │ │ │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ TV M18 │ Program Stack Push │ New program │ COMMAREA Size │
│ │ Completion │ level │ BLL-Cell count │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ TV M19 │ Program Stack Pop │ New program │ COMMAREA Size │
│ │ Completion │ level │ │
│ │ │ │ HANDLE-ABEND: │
│ │ │ │ P-Program │
│ │ │ │ L-Label, │
│ │ │ │ I-Inactive │
│ │ │ │ A-Active │
│ │ │ │ D-Deactivated │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ TV M45 │ Save working storage │ Length of │ PPT Index │
│ │ │ Working Storage │ │
│ │ │ │ Flag: T-temp │
│ │ │ Module Handle │ P-Resident │
│ │ │ │ C-called │
├─────────┼──────────────────────┼─────────────────┼─────────────────┤
│ TV M46 │ Restore │ Length of │ PPT Index │
│ │ working storage │ Working Storage │ │
│ │ │ │ Flag: T-temp │
│ │ │ Module Handle │ P-Resident │
│ │ │ │ C-called │
└─────────┴──────────────────────┴─────────────────┴─────────────────┘
**************************************************************
**************************************************************
*** ***
*** End of PTF 7 updates. ***
*** Updates for previous PTFs follow. ***
*** ***
**************************************************************
**************************************************************
i
README.TXT FOR
CICS OS/2 1.2.0 SERVICE LEVEL 6
3 March 1991
TABLE OF CONTENTS
_________________
Introduction . . . . . . . . . . . . . . . . . . . . . 1
Current Level . . . . . . . . . . . . . . . . . . . . . 1
iiAPAR Information . . . . . . . . . . . . . . . . . . 1
New CICSRUN.CMD Environment Variable use . . . . . . 1
TRAP000D using CECI w/FC Commands . . . . . . . . . . 2
UNEXPECTED REVERSE VIDEO FIELDS IN BMS MAPS . . . . . 2
Using CICS OS/2 with MICROFOCUS COBOL/2 2.4.XX Level 2
New Information APAR . . . . . . . . . . . . . . . . 2
Hints and other information. . . . . . . . . . . . . . 2
1
INTRODUCTION
____________
Nil.
CURRENT LEVEL
_____________
The current level of CICS OS/2 is 1.2.0. Service Level 6
IIAPAR INFORMATION
__________________
The following is the latest from information APAR No.
ii04748:
NEW CICSRUN.CMD ENVIRONMENT VARIABLE USE
With the release of PTF04 (UL85512/UL85513) there is a new
CICSRUN.CMD file. This file is designed to be compatible
with the CICSRUN.CMD file released with earlier versions of
CICS OS/2. (If you have made changes to your existing
CICSRUN.CMD you may also need to make those changes to the
new version.)
This new version of CICSRUN.CMD is designed to be used with
two new files (CICSENV.CMD and CICSDEV.CMD) which are used
to define all the environment variables that CICS OS/2
requires in a run-time and development systems respectively.
All new users to CICS OS/2 will use these files.
Existing users who wish to take advantage of the new
mechanism will need to perform CICSINST for the complete
system.
The new files are *NOT* created by the application of the
PTF alone (CICSINST /PTF).
HOST TO CICS OS/2 COMMUNICATIONS.
When communicating from Host CICS to CICS OS/2 users should
be aware that certain OEM (Third Party) Security Products
may prevent correct operation.
Host security packages which modify ISC and MRO requests may
have these requests rejected by CICS OS/2.
If the request is not a standard CICS formatted request.
For example some products append a USERID Profile Message
which causes the request to be rejected by CICS OS/2.
Consult your OEM supplier for more information.
2
TRAP000D USING CECI W/FC COMMANDS
It is possible to get TRAP00D when using the CECI
transaction with File Control Commands when routing the
command to a remote system. This occurs due to a too large
length or length value being used such as data or key
length. The following circumstances can produce the
problem:
1. file with record length greater than 100 and &data not
set explicitly but left to default.
2. key length set incorrectly (key length is 4) for
instance:
a. keyl(&k)
b. &k 4
this results in &k being set to a large value - it
should be set as follows:
c. keyl(&k)
d. &k h
e. &k +00004
UNEXPECTED REVERSE VIDEO FIELDS IN BMS MAPS
If fields in your BMS maps are set to (for example) reverse
video when you did not expect it, check that you have set
the map I/O buffer to low values to initialise the map
attributes before the send map command.
USING CICS OS/2 WITH MICROFOCUS COBOL/2 2.4.XX LEVEL
When using both CICS OS/2 and MICROFOCUS COBOL/2 at a 2.4.XX
level, the COBLIB.DLL files provided by the 2 products are
different.
CICS OS/2 can run happily with the newer MICROFOCUS COBOL/2
level of the file, but MICROFOCUS COBOL/2 may not work
correctly with the older level supplied with CICS OS/2.
The solution is to remove the CICS OS/2 version of the file
from the LIBPATH, and use solely the new MICROFOCUS COBOL
version.
Symptoms include a 165 Load Error from COBOL. NOTE that this
problem is not the only possible cause of a 165 load error.
NEW INFORMATION APAR
The current information APAR will remain open.
HINTS AND OTHER INFORMATION.
____________________________
Nil.
**************************************************************
**************************************************************
*** ***
*** End of PTF 6 updates. ***
*** Updates for previous PTFs follow. ***
*** ***
**************************************************************
**************************************************************
i
README.TXT FOR
CICS OS/2 1.2.0 SERVICE LEVEL 5
11th January 1991
TABLE OF CONTENTS
_________________
Introduction . . . . . . . . . . . . . . . . . . . . . 1
Current Level . . . . . . . . . . . . . . . . . . . . . 1
iiAPAR Information . . . . . . . . . . . . . . . . . . 1
Known Restriction with number of Files . . . . . . . 1
Using CICS OS22 and the Animator . . . . . . . . . . 1
OS/2 SE and EE VERSION 1.3 . . . . . . . . . . . . . 1
FAA1648S Screen File Open Error . . . . . . . . . . . 2
MSG. L2029 on link of 'C' Application Program . . . . 2
New Information APAR . . . . . . . . . . . . . . . . 2
Hints and other information. . . . . . . . . . . . . . 2
1
INTRODUCTION
____________
Nil.
CURRENT LEVEL
_____________
The current level of CICS OS/2 is 1.2.0. Service Level 5.
IIAPAR INFORMATION
__________________
The following is the latest from information APAR No.
II04598:
KNOWN RESTRICTION WITH NUMBER OF FILES
There is a known restriction within CICS OS/2 that:
1 recoverable transaction can have a maximum 12 (twelve)
recoverable files.
this restriction does not apply to unrecoverable files.
USING CICS OS22 AND THE ANIMATOR
When trying to run CICS OS/2 with Animator to debug (CICSRUN
/D-V123(ANIM)). Problems can occur if the 'COBOL.DIR' file
contains the statement 'ANIM'.
This is caused by Animator becoming confused by two 'ANIM'
statements. ie. one in COBOL.DIR and one part of the
CICSRUN.
The symptoms for this scenario vary from version to version:
error: cannot specify ANIM and RNIM
Animator invalid directive
CICS OS/2 debug session terminates abnormally.
MICROFOCUS are aware of the problem.
OS/2 SE AND EE VERSION 1.3
In order to run with either of the above versions of the
operating system, CICS OS/2 must have PTF04 applied, ie:
UL85512 for a MVS host;
UL85513 for a VSE host.
2
FAA1648S SCREEN FILE OPEN ERROR
On initial start up of CICS OS/2 after installation this
message may occur if your current default is not the
CICS120\OS2DSD SUB-DIRECTORY. ie.
C:> CICS120\OS2DSD\CICSRUN
INSTEAD OF
C:> CD CICS120\OS2DSD
C:> CICSRUN
To resolve this do the following:
start CICS OS/2 from the correct default
using CEDA amend the FCT entry for file FAAMSFSC.BTR to
include a full directory path name.
You should then be able to start CICS from any sub-directory
(after the next start of CICS!)
MSG. L2029 ON LINK OF 'C' APPLICATION PROGRAM
If the following messages are issued during the link phase
when using CICSCLNK or CICSCTCL:
"... ERROR L2029 : '_FAAMAIN' : UNRESOLVED EXTERNAL"
"... ERROR L2029 : '_FAAINIT' : UNRESOLVED EXTERNAL"
The possibility should be investigated that during the
translate phase (using CICSCTRN or CICSCTCL) the 'MAIN'
option was not specified for a MAIN() program. For further
information see SC33-0616-2 SAG page 325.
NEW INFORMATION APAR
The new information APAR is ii04748.
HINTS AND OTHER INFORMATION.
____________________________
Nil.
**************************************************************
**************************************************************
*** ***
*** End of PTF 5 updates. ***
*** Updates for previous PTFs follow. ***
*** ***
**************************************************************
**************************************************************
i
README.TXT FOR
CICS OS/2 1.2.0 SERVICE LEVEL 4
9 November 1990
TABLE OF CONTENTS
_________________
Introduction . . . . . . . . . . . . . . . . . . . . . .
Current Level . . . . . . . . . . . . . . . . . . . . . .
iiAPAR Information . . . . . . . . . . . . . . . . . . 1
Service Installation Documentation . . . . . . . . . 1
TRAP000C on CICSRUN start up . . . . . . . . . . . . 1
CICS OS/2 not releasing DLLS. . . . . . . . . . . . . 2
CICSHELP - F3 / 'THAT KEYSTROKE HAS NO MEANING' . . . 2
TRAP 000D during STARTUP / INITIALISATION of CICS OS/2 2
MSGDFH4412 'INVALID TRANSID' when TRANSACTION ROUTING 3
LINKEDIT MESSAGE L2022 when using CICSTCL . . . . . . 3
ERROR MESSAGES when starting CICS OS/2 in LAN SERVER
ENVIRONMENT . . . . . . . . . . . . . . . . . . . . 3
3151 ASCII TERMINAL SUPPORT in CICS OS/2 . . . . . . 4
3270 Data Streams (EBCDIC Coordinates) . . . . . . . 4
New Information APAR . . . . . . . . . . . . . . . . 4
Hints and other information. . . . . . . . . . . . . . 5
New Start-up Methodology . . . . . . . . . . . . . . 5
New Message (to assist with problem resolution) . . . 6
Reporting problems via IBM Level 1 and PMR . . . . . 7
Communications Setup . . . . . . . . . . . . . . . . 7
User Exits - FAAEXP02 and FAAEXP04 . . . . . . . . . . 7
'Cooperative Processing with CICS OS/2' . . . . . . . 7
Trace Points . . . . . . . . . . . . . . . . . . . . . 8
Function Number . . . . . . . . . . . . . . . . . . . 13
1
INTRODUCTION
____________
In future service deliverables of CICS OS/2 the README.TXT
file will contain considerably more information if
necessary. The README file will be used as a means of
keeping you updated with the very latest information plus
any additional documentary information that the CICS OS/2
Development team wish to release.
Each README
will contain a reference to an existing information APAR
that customers and IBM SEs may reference through IBM
level 1 support. This information APAR will be updated
by CICS OS/2 developers and Service team and will
contain tips, hints, work-arounds and other fixes which
may be relevant to the customer.
will also contain details from the previous information
APAR.
Each new information APAR will contain a reference to the
previous information APAR. Thus users will be able to chain
through the existing information APARs.
CURRENT LEVEL
_____________
The current level of CICS OS/2 is 1.2.0. Service Level 4.
IIAPAR INFORMATION
__________________
The following is the latest from information APAR No.
II04482:
oo SERVICE INSTALLATION DOCUMENTATION
Chapter 9 Page 59 Point 5 for MVS host systems
reads
receive faaptfnn.cmd a:'cics120.cmd(faaptfnn)'
should read
receive faaptfnn.cmd a:'cics120.mts(faaptfnn)'
oo TRAP000C ON CICSRUN START UP
If CONFIG.SYS contains line IOPL=NO this causes CICS OS/2 to
trap 000c stack segment error when started with CICSRUN.
solution: SET IOPL=YES
2
oo CICS OS/2 NOT RELEASING DLLS.
There are some cases when the DLLs are not released by CICS
OS/2 after successful completion of the transaction. This is
because of compatibility problems between different versions
of the COBOL compiler. Programs compiled with the IBM COBOL
1.02 compiler do not get unloaded after being run.
oo CICSHELP - F3 / 'THAT KEYSTROKE HAS NO MEANING'
This occurs because you have run CICSHELP outside of the
correct directory - to avoid this run CICSHELP from the
directory CICS120/OS2DSD - F3 will then work correctly. If
you do run CICSHELP outside the correct directory use
CTRL-BREAK to exit from the help panel.
oo TRAP 000D DURING STARTUP / INITIALISATION OF CICS OS/2
Problems can arise due to the incorrect setting of
environment variables which cause CICS OS/2 to trap during
CICSRUN.
If you are experiencing this you may like to try the
following to startup a 'vanilla' CICS system without the
whistles and bells.
1. in CONFIG.SYS remove all CICS OS/2 environment variables
except LIBPATH. LIBPATH should be set up to include the
following:
;.;X:\CICS120\OS2DSD; where