home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
o22516d1.zip
/
CIC2UDRN.DOC
< prev
next >
Wrap
Text File
|
1994-01-05
|
76KB
|
1,837 lines
=========================================================================
C I C S O S / 2 O P T I O N
f o r
M I C R O F O C U S C O B O L W O R K B E N C H
V2.5.16
=========================================================================
RELEASE NOTES
==============
TABLE OF CONTENTS
=================
ESSENTIAL INFORMATION
INTRODUCTION
IMPORTANT NOTES
Syncpoint Coordination
Multiple Session Debugger
Changes due to Fix for APAR PN24821
Updating your System with New\Changed IBM RDO definition
ERRORS FIXED IN THIS RELEASE
ENHANCEMENTS IN THIS RELEASE
KNOWN ERRORS IN THIS RELEASE
DOCUMENTATION OMISSIONS AND ERRORS
CICS OS/2 OPTION SYNCPOINT COORDINATION
Overview
Software Requirements
Components
Using Syncpoint Coordination
Micro Focus IMSVS86 Support
IBM OS/2 Database Manager Support
XDB Systems, Inc. Extended Database System Support
Error Messages
Trace Entry Documentation
CICS OS/2 OPTION EXECUTION TIME CONTROL (MC2INIT)
Overview
Components
Using MC2INIT
Configuration File
Process Control Parameters
Example MCO2.CFG Files
Debugging PM-API Processes
Restrictions in Related Software
Error Messages
PRODUCT CHECKLIST
INSTALLATION
DISK CONTENTS
ESSENTIAL INFORMATION
=====================
o The method for loading debuggers in CICS OS/2 has changed. You must
insure that the CICSWRK environment variable is changed to include
the COBOL directories that contain animate.exe, xil.exe, animate.lbr
and xilerate.lbr. By default these directories are COBOL\EXEDLL and
COBOL\LBR. However, this may have been customized during installation
of your COBOL system.
-PAO14818 added V2.5.15
o It is essential that you read the section "Changes due to Fix for
APAR PN24821" in these Release Notes.
o As of PTF-23 IBM recompiled the CICS OS/2 system code with version
3.0.54 of the Micro Focus compiler. This means that you must have
that level or higher on your machine to insure compatibility with
this update.
INTRODUCTION
============
This version of CICS OS/2 Option for Micro Focus COBOL/2 Workbench is a
maintenance release for version V2.5.04 of CICS OS/2 Option for Micro
Focus COBOL/2 Workbench, fixing the problems indicated below. It is
issued as an update disk rather than a full disk set, and requires the
V2.5.04 disk set for a complete installation.
Note: From October 1992, each new entry in Release Notes states the
reference number of the problem or enhancement request that gave
rise to it. This is to enable Product Support to help you more
quickly if you should need to call them. These numbers are usually
Product Discrepancy Report (PDR) numbers. A note of the release at
which the entry first appeared in the Release Notes appears either
with the PDR number or beneath the section heading.
Other minor improvements in formatting are also being made
starting from October 1992.
Note: From January 1993, the section "Errors Fixed in This Release"
includes errors fixed by IBM PTF's, since not all such fixes are
necessarily shown in the IBMPTFnn.DOC file.
IMPORTANT NOTES
===============
Syncpoint Coordination
======================
If you have been using the Syncpoint Coordination feature, before
applying this update disk you must backup or rename files FAAOIS04.xxx
and FAAOISPT.xxx; this is because the update process automatically
restores them to their original state. Once the update process has
finished, you can replace these new files with the copies you made before
the update process was started.
Multiple Session Debugger
=========================
If you have been using the Multiple Session Debugger, before applying
this update disk you must backup or rename the file MCO2.CFG if it has
been customized; this is because the update process restores this file so
that the Multiple Session Debugger feature is not available. Once the
update process has finished, you can replace the new MCO2.CFG file with
the copy you made before the update process was started.
You must also replace the file FAAOMPML.EXE with the file FAAOMPML.EXA;
this is because the update process restores FAAOMPML.EXE such that it
only supports a single debugging session. Once the update process has
finished, you must rename or copy the file FAAOMPML.EXA to FAAOMPML.EXE.
Note: To bring CICS OS/2 into line with host CICS, access to record zero
in Relative Record (RRDS) files is no longer supported.
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 PTF22.
*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.
-PN24821 added V2.5.12
Updating your System with New\Changed IBM RDO definition
--------------------------------------------------------
Note: If you are updating from V2.5.13 there are no additional PTF's
that need to be imported. You can ignore this section.
Because IBM periodically supplies maintenance to the RDO file
(FAACTFTB.BTR), you must take special action to insure your resource
definition file (FAACTFTB.BTR) picks up all IBM maintenance that required
distinct user action. After installing the CICS OS/2 V2.5.15 update, you
need to use the CAIM import transaction to pick up the maintenance.
1. Make the DATA directory of the target CICS OS/2 system the current
directory (for example, CICS120\OS2DSD\DATA) and rename file
FAAAEFIE.BTR to FAAAEFIE.xxx, where xxx makes the filename unique.
Then rename FAAAEFIE.T01 to FAAAEFIE.BTR. Now cold-start CICS OS/2
(note you must COLD-start it), sign-on and issue the CAIM
transaction.
2. At the import panel, enter the appropriate PTF in the group name
field. Set all fields to N and press enter. This transaction will
import the required maintenance introduced by this APAR. Warning
messages will be written to temporary storage queue CEBRXXX (where
XXXX is the id of the terminal issuing the transaction. You can
ignore these messages.
3. The following is a list of IBM PTF's that have been introduced since
PTF-9.
PN21505 : PTF-18
PN28420 : PTF-19
PN29610 : PTF-20
PN15480 : PTF-15
4. Shutdown CICS OS/2 with a CQIT. When CICS OS/2 terminates, go to the
DATA directory of the target CICS OS/2 system and rename FAAAEFIE.BTR
back to FAAAEFIE.T01 and FAAAEFIE.xxx back to FAAAEFIE.BTR.
It is essential that you follow these procedures so that you incorporate
all required IBM maintenance to the resource definition file.
-NWB20645 added V2.5.13 amended V2.5.15
ERRORS FIXED IN THIS RELEASE
============================
The following errors are fixed in this release.
o Data item with a VALUE clause containing the text "COPY" caused
the integrated proprocessor to mistakenly assume a COPY-file had
to be expanded.
-NWB24254
Fixed by IBM PTF 29
----------V2.5.16--
o EIBCONF FIELD IS NOT RESET AFTER AN ISSUE ERROR COMMAND
-PN41088
o CICS OS/2 ENVIRONMENT VARIABLE CICSTEXT IS NOT WORKING.
-PN32909
o CAEX GETS ABENDAEIV
-PN38509
o IF FIELDS IN A MAP NOT IN ASCENDING ORDER, A RECEIVE MAP WILL NOT
PICK UP THE OUT OF SEQUENCE FIELDS.
-PN39349
o SEND CONTROL CURSOR NOT RIGHT AFTER SEND MAP
-PN42673
o WITH EXEC CICS, ADDRESS IN DUMP IS GARBAGED
-PN43265
o CICS OS/2 TRANSLATOR DOES NOT CHECK FOR SPELLING ON THE PROCEDURE
DIVISION STATEMENT.
-PN44008
o 55H0X TRACE POINTS ARE IDENTIFIED AS ENTRY TRACE POINTS INSTEAD OF
EVENT TRACEPOINTS.
-PN44445
o RECEIVE FUNCTION CAN'T USE CORRECTLY WITH OPTION NOTRANCATE.
-PN44826
o UPON COMPLETION OF TRANSACTION ROUTING FROM THE HOST, THE HOST
SYSTEM LOSES ITS EXTENDED ATTRIBUTES
-PN45744
Fixed by IBM PTF 28
----------V2.5.16--
o TRANSACTION ROUTE RETURN OF MAP DOES NOT DISPLAY THE MAP
-PN18013
o MAPFAIL CONDITION MAY ARISE WHEN USING EDF.
-PN40951
o COMMAREA IS LOST WHEN PASSED TO A THIRD PROGRAM.
-PN39680
o EXEC CICS ABEND DOES NOT END THE PROGRAM
-PN40959
o AFTER INSTALLING PTF24, MSGFAA2251E OCCURS AT SIGNON
-PN39862
o USING A DOLLAR SIGN WITH JUSTIFY RIGHT ZERO,THE $ IS NOT HOLDING ITS
POSITION LIKE THE HOST
-PN36679
o SYS3175 TRAP000D IN FAASRSML WHEN ATTEMPTING TO ACCESS ANOTHER SYSTEM
ACROSS AN LU62 LINK.
-PN37466
o CICS OS/2 BMS MAP TRANSLATOR FAILS TO FLAG A LENGTH IF THE POS/FIELD
LENGTH EXCEEDS LINELENGTH.
-PN38181
o BMS GRPNAME FIELDS ARE NOT PROPERLY DISPLAYED IN CICS OS/2.
-PN39300
o DOSTYMERASYNC CALL RETURNING UNEXPECTED BINARY ZEROS. RESULT IS EXEC
CICS CANCEL DOES NOT CLEAR EXEC CICS DELAY
-PN43234
Fixed by IBM PTF 27
----------V2.5.16--
o AFTER APPC CONFIRM FROM HOST AND CICS OS/2 XACT DOES AN EXEC CICS
ISSUE ABEND, CICS OS/2 SENDS APPC DEALLOCATE W/O ABEND.
-PN16639
o TRANSACTION ROUTE RETURN OF MAP DOES NOT DISPLAY THE MAP.
-PN18013
o CICS OS/2 V1.2 DOES NOT ALLOW DOSKILLPROCESS COMMANDS TO BRING DOWN
HUNG TASKS.
-PN41208
o A CICS OS/2 TASK DOING RETRIES TO ALLOCATE A SESSION THRU COMM MGR
DOES NOT RELEASE A SEMAPHORE.
-PN35314
o SYNCONRETURN PARM IS NOT PASSED ON A DAISY CHAINED DPL CALL.
-PN35526
o MAP TRANSLATOR INCORRECTLY CALCULATES LENGTH FOR PICIN='S9(8)'
INCORRECTLY AND ISSUES MSGFAA1073.
-PN35880
o SET 'ADDRESS OF' IS A COBOL2 STATEMENT AND SHOULD BE FLAGGED AS
INVALID IF THE COBOL2 TRANSLATOR DIRECTIVE IS NOT SET.
-PN36901
o WRONG TRANSLATOR OUTPUT ON COBOL EVALUATE FUNCTION.
-PN37816
o THE CICS COBOL TRANSLATOR WILL LOOP IF THE EXEC CICS RETURN COMMAND
DOES NOT HAVE AN END-EXEC STATEMENT.
-PN38304
Added in V2.5.15
================
The fixes listed in this and any following similar section(s), which were
included in earlier maintenance releases, are also in this release.
o This update disk includes fixes included in IBM PTF23, PTF24, PTF25
and PTF26. Details of these fixes are in the IBM on-disk document
IBMPTF26.DOC.
o mc2sync0 did not terminate IMS properly at system shutdown if IMS
was started by FAAOIS04 at initialization. This resulted in system
hangs during subsequent restarts.
-PAO13731
o Exiting to Workbench and then coming back to the CICS OS/2 Option
main menu gave a load failure on DIRECT.GNT.
-PAO11743 & PAO13532
o Reverse mono fields were not highlighted when set to bright.
-PAO10957
o You got a protection violation on MC2sync0 when animating a DBM SQL
program.
-PAO12094
o DFHCNV generated incorrect output if the last elementary item in a
data structure was a FILLER.
-PAOO13550
o During preprocessing, if the .CCP and .CBL files were found to be out
of synchronization with each other, the preprocessor stopped with a
run-time error 153 ("Subscript out of range"). This has been
corrected so that a termination message is displayed and the
compilation stops.
-PAO13395
o You could not set an Animator breakpoint on lines containing the
keyword DFHRESP, DFHRESP2, or DFHVALUE.
-PAO13399
o Checking MCCTxx demo programs with the Structured Animator toggle set
gave the error message "**dd fatal error writing to dynamic memory".
-PAO13895
o COPY/REPLACING did not work with an integrated preprocessor.
-PAO13078
o When the CICS Translator finished with a non-zero return code,
compiling continued nevertheless. This has been corrected so that the
generated COBOL source program is not compiled.
-PAO13067
o The ALIGN(2) directive has been removed from the supplied CICSOS2.DIR
The default of ALIGN(8) will now be in effect. The ALIGN(2) setting
is incompatible with DBM and caused large unidentifiable SQL return
codes.
-NWB23281
Fixed by IBM PTF 26
----------V2.5.15--
o AFTER APPC CONFIRM FROM HOST AND CICS OS/2 XACT DOES AN EXEC CICS
ISSUE ABEND, CICS OS/2 SENDS APPC DEALLOCATE W/O ABEND.
-PN16639
o EXEX CICS START TRANID=,REQID= WHICH IS THE SAME AS THE
RUNNING XACTION WILL GET INVREQ.
-PN33041
o OPEN RESET TO BASE FILE WITHOUT CLOSING ITS ALTERNATE INDICES
RESULTS IN INVREQ AND FILE CORRUPTION.
-PN33061
o IF A PEER TO PEER TRANSACTION ROUTING REQUEST FAILS, THE
INITIATING SESSION HANGS.
-PN33170
o MESSGAE FAA0558W IN C-TRANSLATOR.
-PN33549
o EXEC RECEIVE OF TERMINAL DATA UNDER CEDF IS RETURNED WITH A
LENGTH AND DATA WHICH IS 3 BYTES LONGER THAN WHEN NON CEDF.
-PN34017
o TRANSLATOR INCORRECTLY REPLACES DATA FOR A COPY REPLACE.
-PN35466
o SYNCPOINT ROLLBACK IS FAILING ON A FILE AFTER OPEN RESET.
-PN35467
o CICS OS/2 COBOL TRANSLATOR INCORRECTLY PARTIALLY REPLACES
DATA ON WHAT SHOULD BE A FULL COPY REPLACE.
-PN37307
Fixed by IBM PTF 25
----------V2.5.15--
o REVERSE MONO FIELDS NOT HIGHLIGHTED WHEN SET BRIGHT.
-PN18314
o ABENDAZI4 ATTEMPTING TO USE AN LU2 LINK.
-PN20555
o CICS OS/2 SEND MAP ERASEAUP GENERATES A SEND MAP ERASAUP/PRING/ALARM.
-PN29974
o E.C.SEND MAP WITHOUT SPECIFYING A CURSOR ADDRESS,AFTER AN E.C.
SEND MAP WITH CURSOR ADDRESS:CURSOR NOT AT HOME POSITION.
-PN30330
o INSUFFICIENT RESOURCES ATTEMPTING TO USE ETI
-PN30850
o SENDING A BMS MAP IN TRANSACTION ROUTING FROM CICS/VSE TO CICS/OS2
RANDOMLY THE MAP IS PRINDED RANDOMLY ON LOCAL PRINTER.
-PN31474
o IF AN LU2 CONNECTION GOES DOWN, THE CICS OS/2 SESSION USING THE
CONNECTION WILL HANG.
-PN32329
o CICSMAP ISSUES MSGFAA1975W IN ERROR FOR A MAP WHEN THE LENGTH FIELD
FOLLOWS THE INITIAL AND ATTRB FIELDS.
-PN32860
o PROCEDURE DIVISION STATEMENT NOT BUILT CORRECTLY IF THE USING PARM
IS USED AND PERIOD IS ON A DIFFERENT LINE.
-PN33383
o AN ECI CALL WHICH LINKS TO A PROGRAM WHICH DOES NOT EXIST RETURNS
ABENDAEIO (DUPKEY) RATHER THAN ABENDAEI0(PGMIDERR).
-PN33670
o TRANSLATOR DOES NOT PUT OUT AN ERROR MESSAGE WHEN A PROGRAM USES AN
ALPHA LITERAL FOR THE LENGTH OPTION.
-PN33866
o TRANSLATOR GIVES ERROR FAA0173E INCORRECTLY WHEN USING A VARIABLE
WITH AN ALPHA CHARACTER FOR THE LENGTH OPTION.
-PN33867
o CICS OS/2 RELEASE 1.20 DOES NOT SUPPORT THE CSET/2 COMPILER.
-PN35770
Fixed by IBM PTF 24
----------V2.5.15--
o TRANSLATOR GIVES ERROR FAA0173E INCORRECTLY WHEN USING A VARIABLE
WITH AN ALPHA CHARACTER FOR THE LENGTH OPTION.
-PN33867
o AN EXEC CICS ENQUEUE RESOURCE WILL HANG CICS OS/2 AT PTF23.
-PN36110
o SEND TEXT WITHOUT THE ERASE OPTION CAUSES THE SCREEN TO CLEAR.
-PN36202
Fixed by IBM PTF 23
----------V2.5.15--
o PRINTING A 132 COLUMNS FILE UNDER CICS/OS2 THE FIELDS LENGTH ARE
NOT RESPECTED.
-PN21953
o SOURCE FILE IS MISSING FOR SAMPLE PROGRAM FAAUTPUC.
-PN13891
o EXTENDED ATTRIBUTES ARE NOT RESET WHEN REPLACED WITH AN ORDER THAT
HAS NO EXTENDED ATTRIBUTES.
-PN18313
o IF ATTRIBUTES ARE ENTERED INTO A BMS MAP ATTR FIELD THE ATTRIBUTES
MAY BE IGNORED ON THE MAP SEND/RECEIVE.
-PN27313
o DURING SHUTDOWN, VARIOUS TRAP 00D'S OCCUR.
-PN27866
o EIBFN SET TO X'1002' = ASKTIME AT RE ENTRY INTO A
PSEUDO-CONVERSATIONAL TRANSACTION, AFTER PTF16.
-PN28226
o CURSOR POSITIONING WRONG
-PN29419
o ON A START TRANSACTION FROM A HOST CICS 3.3 SYSTEM, AN ABENDATNI
OCCURS AFTER A DEALLOCATE NORMAL IS RETURNED.
-PN29609
o 3270 DATASTREAM MONO FIELDS ARE BEING DISPLAYED IN 4-COLOR MODE WHEN
THERE ARE EXTENDED COLORS PLACED ON THE SCREEN AFTER PTF19.
-PN30284
o WRITE TO A FILE WITH SYSID GIVES OK RESPONSE TO WRITE AND THEN GETS
ABENDATNI.
-PN30412
o INVALID USE OF SET OPERAND OF EXEC CICS LOAD PROGRAM PRODUCES BAD
OUTPUT BUT NOT ERROR MESSAGE.
-PN30651
o WITH STARTRE/REQID, IF THE BROWSE IS INTERRUPTED WITH A DIRECT READ,
THE NEXT READNEXT GETS RECORD OF THE DIRECT READ +1.
-PN31179
o CICS OS/2 ISSUED MESSAGE FAA2220 INTERNAL COMMUNICATIONS ERROR WHILE
TRANSACTION ROUTING.
-PN31190
o SHUTDOWN OF OS/2 2.0 WILL NOT COMPLETE IF CICS OS/2 IS RUNNING.
-PN31864
o FILE THAT HAS A CLOSE WAIT AND OPEN RESET DONE CANNOT BE USED BY
ANOTHER TASK, NOTOPEN IS RETURNED.
-PN32146
o TRANSACTION TRIGGERED FROM TDQ WRITE FROM HOST CICS REQUIRES ENTER
KEY TO FREE TERMINAL SESSION AND RELEASE TDQ ENQUEUE.
-PN32292
o CICS OS/2 DOES NOT CURRENTLY SUPPORT ANIMATOR/2.
-PN32910
o IF A TEMPSTORE CI SIZE OF 32767 IS SET IN THE SIT, A TRAPD WILL
OCCUR WHEN YOU ATTEMPT TO RUN A TRANSACTION.
-PN33220
o TRANSLATOR GIVES ERROR FAA0173E INCORRECTLY WHEN USING A VARIABLE
WITH AN ALPHA CHARACTER FOR THE LENGTH OPTION.
-PN33867
o AN EXEC CICS ENQUEUE RESOURCE WILL HANG CICS OS/2 AT PTF23.
-PN36110
Added in V2.5.13
================
o The CICS Translator reserved word DFHVALUE was not recognized by the
integrated preprocessor.
-PAO11326
o The DFHCNV process returned incorrect results in certain
circumstances.
-PAO12977
Fixed by IBM PTF 22
----------V2.5.13--
o PEER TO PEER NETBIOS COMMUNICATIONS FAIL UNDER OS/2 2.0.
-PN21507
Added before V2.5.13
====================
o This update disk includes fixes included in IBM PTF22. Details of
these fixes are in the IBM on-disk document IBMPTF22.DOC. This IBM
PTF includes enhancements made to the External Call Interface (ECI)
to CICS OS/2. Details of this enhancement can be found in the
document ECI.DOC which is in your OS2DSD subdirectory.
o DFHCNV macro generation has been changed to generate a data type of
PD for zoned decimal fields, for example PIC S9(4) fields.
-PAO12503 added V2.5.12
o If you were using Workbench V3.0, CICS OS/2 sessions sometimes hung
if you started CICS OS/2 online using the Multiple Session Debugger
facility in CICS OS/2 Option.
o CICSTCL.CMD used COBOL.LIB instead of COBLIB.LIB.
o The preprocessor imposed a limit of 80 characters on the length of a
COBOL source line. The correct limit of 255 is now used.
o The preprocessor returned an error if you tried to use the CICSTRL
environment variable.
o When in BMSSCRNS, setting the EXTATT mapset verb to YES did not
generate the attribute fields (C, P, H, and V) in the COBOL copybook.
o When in BMSSCRNS, map-names of seven characters were sometimes
truncated to six characters if the Insert key was on when the map
was named or renamed.
o When in BMSSCRNS, repeatedly saving and generating mapsets resulted
in the first map in the set being deleted and replaced with a copy of
the last map in the set.
ENHANCEMENTS IN THIS RELEASE
============================
The following enhancements are made in this release.
o The IBM CICS Translator directive NOPROCESSCOPY is now supported when
you compile using the integrated preprocessor.
-PAO11633
o The integrated preprocessor now supports COPY statements in the
Procedure Division, provided the COPY-files do not contain EXEC CICS,
SERVICE RELOAD, DFHRESP, DFHRESP2, or DFHVALUE statements.
-PAO11633
Added in V2.5.13
================
The enhancements listed in this and any following similar section(s),
which were included in earlier maintenance releases, are also in this
release.
None.
Added before V2.5.13
====================
o This update disk includes the IBM-supplied batch files CICSCOMP,
CICSTCL and CICSLINK. These .CMD files enable you to perform batch
translate, compile and links easier.
o This release contains a demonstration of CICS OS/2 Option working in
conjunction with the Common Communications Interface (CCI) and Dialog
System. To install this demonstration you should perform the
following steps:
o copy the file DSDEMO.@IP from the installation disk into a
temporary directory on your computer
o make the temporary directory your current directory, and enter:
pkunzip dsdemo.@ip
o read the file DSDEMO.DOC on how to set up and run the
demonstration suite of programs.
o This release of CICS OS/2 Option for Micro Focus COBOL/2 Workbench
features syncpoint coordination. This enhances CICS OS/2 interfacing
to Micro Focus IMSVS86, IBM Database Manager (DBM), and XDB Systems
Extended Database System (XDB). For further details on syncpoint
coordination see section CICS OS/2 Option Syncpoint Coordination in
this on-disk document.
o This release of CICS OS/2 Option for Micro Focus COBOL/2 Workbench
features CICS OS/2 Option Execution Control (MC2INIT). This provides
added control to CICS OS/2 startup, offering greater control over
debugging and the run-time environment. For further details on
MC2INIT see section CICS OS/2 Option Execution Control (MC2INIT) in
this on-disk document.
o The Filecopy utility can be used to convert Btrieve format files into
Micro Focus format, and vice versa.
o Support has been added for Call- and Exec-level DL/1 when used in
conjunction with the ASCII version of the Micro Focus IMS Option.
o Support has been added for the ASCII version of the XDB database,
which closely emulates the functionality of IBM's DB2 database.
o You can use the CICS OS/2 Option DFHCNV Generator to generate DFHCNV
macros for translating data between EBCDIC (mainframe) and ASCII
(PC).
o The BMS Screens utility can be used to create BMS macros. Its
powerful screen painting functions include block move, cut and paste,
as well as the ability to set text video attributes such as color,
intensity, reverse video, and blinking.
KNOWN ERRORS IN THIS RELEASE
============================
o If you get a load failure 173 on DIRECT.GNT after executing certain
main menu functions, you can correct it by amending MCMENU.MNU. Add
an :OPT-LIBRARY entry as follows to the section of the menu that
returned this error:
opt-library: $COBDIR\COBCLI.LBR
Delete or rename the current MCMENU.MNT and restart the CICS OS/2
Micro Focus menu.
-PAO11743 & PAO13532 added V2.5.15
o If you are using a Beta version of COBOL Workbench V3.0, the
ANIM:USERSESSION"PM"
command does not work. To solve this problem you should use the
ANIM:
command.
o To use Xilerator from Micro Focus Toolset V2.5 with this CICS OS/2
Option system you must copy the file XIL.EXE to a new file name
called PXIL.EXE.
o If you invoke the Mainframe Development Menu Workbench from the F10
key on the CICS OS/2 Option main menu, CICS OS/2 Option functions are
not available when you return to CICS OS/2 Option.
You can solve this problem by editing the file MCMENU.MNU. You
should change line 33 from:
F10 :RUN: CLI
to:
F10 :CALL-MENU: CLI.MNU
You should then delete the file MCMENU.MNT.
o A system hang occurs if you use F3=CICS+CHECK on a program that
contains either $SET SQL or COBOL/2 dynamic calls.
To perform either of these functions you should use the separate
options F4=Trans, and F5=Compile.
o Before you can use the supplied FCPY transactions you must run the
FDAT.BMS file through the IBM BMS translator to generate a mapset
file.
o Copying a COBOL/2 file to a new CICS OS/2 VSAM file does not behave
as documented on page 9-5 of the CICS OS/2 Option for Micro Focus
COBOL/2 Workbench User Guide.
To copy from a COBOL/2 file to a new CICS OS/2 VSAM file you should
do the following:
- Define the base KSDS in the FCT with any alternate keys
- Define all the alternate keys in the FCT for the base KSDS
- Close down CICS OS/2 using the CQIT command
- Restart CICS OS/2
- Issue the command:
CECI SET FILE (file-name) OPEN RESET
for the base KSDS
- Issue the command:
CECI SET FILE (file-name) CLOSED
for all alternate indexes
- Process the FCPY transaction to load the base KSDS
- Issue the command:
CECI SET FILE (file-name) CLOSED
for the base KSDS
- Issue the command:
CECI SET FILE (file-name) OPEN
for the base KSDS
- Issue the command:
CECI SET FILE (file-name) OPEN
for all the alernate indexes
DOCUMENTATION OMISSIONS AND ERRORS
==================================
Micro Focus CICS OS/2 Option User Guide
=======================================
Chapter 2 (Installation and Configuration)
------------------------------------------
o Page 2-9. In the section "Workbench Configuration File" in the
chapter "Installation and Configuration", amend the line following
point 5 to read:
extensions ccp cbl cpy bms trl {space}
Chapter 9 (Filecopy)
--------------------
o Page 9-6. Add the following new section:
Copying Mainframe VSAM KSDS File to CICS OS/2
----------------------------------------------
To copy a VSAM KSDS File to CICS OS/2, follow the steps below:
1. Download the file from the mainframe. Do not specify ASCII or
CRLF on the receive command.
2. Use the Workbench File Loader (WFL) to convert the file to
ASCII record sequential (see your Workbench Reference for
further information).
3. In CICS OS/2, create an FCT entry for the CICS OS/2 file you
want to create with FCPY. Specify it as KSDS, and specify the
record lengths and key position(s).
4. Take CICS OS/2 down and restart to make the new resource
definition active.
5. Run FCPY. Set:
CICS file Mode: O
OS/2 file type: F
CICS file name: file-name
OS/2 file name: path to file
Press Enter to create the file.
-NWB20682 added V2.5.13
On-disk Document CICSOSRN.DOC (Release Notes)
=============================================
o The following section should be added after the section
"Introduction":
SECURITY KEYS AND ADD-ON PRODUCTS
This section is only relevant if you have been supplied with
a security key.
Upgradable Security Keys
========================
In the past, each security key could be used in conjunction with
only one software package. This meant that a user running six
separate software packages, each encrypted to run with a
different security key, would need a stack of six security keys
plugged into the back of the machine. With each security key
adding approximately 2 inches to the length of this stack, this
system was often inconvenient and irritating to use.
The problems caused by these long chains of security keys have
been solved by the development of the UPGRADABLE SECURITY KEY.
This allows several encrypted products to use the same security
key at once.
This is how they work.
When you received your original copy of COBOL/2 or Toolset you
also received a Security Key. This is a BASE security key.
With your add-on product you will have been given an ADD-ON
Security key. This security key is useless on its own. However,
it contains the codes required to unscramble the
security-protected add-on, and this information can be
transferred to the BASE security key in a few easy steps. You
will simply need to plug the ADD-ON security key into the BASE
security key and run a simple utility program. Your computer will
then be able to run the add-on product, and you can remove the
ADD-ON security key.
At this point the ADD-ON key cannot be used for another upgrade.
However, you can downgrade the BASE key again onto the ADD-ON
key. If you do this the BASE key will no longer support the
add-on, and you will be able to use the ADD-ON key to upgrade
another BASE key.
It should be clear from this that it is impossible to have more
than one BASE key upgraded by the same ADD-ON key at the same
time. If you want to enable your product on a different machine,
you will first need to disable your product on its current
machine by downgrading onto the original key provided with your
product. So the new system retains the flexibility of the old
system. All that is lost is the inconvenience.
Upgrading and Downgrading the Base Security Key
-----------------------------------------------
Note that if you wish to install the add-on product on another
machine, you will need to do a downgrade on the original machine,
followed by an upgrade on the new one.
Upgrading the Base Key:
1. Plug the Micro Focus BASE security key into the parallel port
on your computer.
2. Plug the ADD-ON security key into the back of the BASE
security key.
3. Check that both security keys are recognized by typing
INSTKEY QUERY
at the command-line. This will display the name of the
product encoded in the ADD-ON security key. The query will
also tell you if it has not sensed either of the two security
keys.
4. Transfer information from the ADD-ON to the BASE security key
with the command-line:
INSTKEY INSTALL
The BASE security key will now support the add-on product as well
as the base product.
Downgrading the Base Key:
Downgrading is achieved in almost exactly the same way, except
that in step 4 you will need to type
INSTKEY DEINSTALL
If you perform an upgrade followed by a downgrade, both the BASE
and the ADD-ON security keys will be in exactly the same state as
they were prior to the upgrade."
o The following section should be added after the section "Restrictions
in the Software":
RUNNING CICS OS/2 IN AN IBM LAN NETBIOS ENVIRONMENT
---------------------------------------------------
o The number of NETBIOS resources defined in Communications
Manager must be at least 40 greater than the number defined
in the IBMLAN.INI file on the LAN server. This difference
must be maintained even if extra resources are used by other
applications. Failure to maintain this difference will result
in unpredictable behavior when trying to use the server.
o The CICS OS/2 system on the LAN server must be on the same
PTF level as the CICS OS/2 system on the node.
On-disk document MC2INIT.DOC
============================
o Add the following note at the end of the section "Using MC2INIT":
Note: The number of Animator or other debugger sessions you can
run simultaneously depends on the amount of memory you
have installed in your machine.
-PAO12010 added V2.5.12
User Guide
==========
Chapter 2 (Installation and Configuration)
------------------------------------------
o The following text should be added at the end of the description of
the BMSMAP environment variable:
BMSMAP is only used by the BMS mapset translator to find this
file. The CICS OS/2 online system uses the FCT to find this file.
If you move FAAMSFSC.BTR to a different directory, change its
entry in the FCT to show the new path.
CICS OS/2 OPTION SYNCPOINT COORDINATION
=======================================
Overview
========
This section should be regarded as an additional section to your CICS
OS/2 Option User Guide. It describes Syncpoint Coordination, which
enhances CICS OS/2 interfacing to Micro Focus IMSVS86, IBM Database
Manager (DBM) and/or XDB Systems Extended Database System (XDB).
It enables applications using these systems to behave like similar
370-based applications using IMS or DB2. The Syncpoint Coordination
feature also takes over connecting to and starting IMSVS86, DBM and XDB.
It provides the following extra functions for CICS OS/2:
o Implicit Commit for IMS, DBM and XDB databases at end of CICS task.
o Rollback for IMS, DBM and XDB databases at CICS task abend.
o "Start database using" for a specific DBM database at CICS OS/2 start
if requested.
o Commit or Rollback of IMS, DBM and XDB databases at CICS Syncpoint
based on whether ROLLBACK was requested or ROLLEDBACK was signaled.
o Support for more than one DBM database during a single execution of
CICS OS/2.
o Support of DBM calls from .INT and .GNT code.
o Optional automatic restart of a DBM database that was not closed
properly during the previous execution.
o Optional user logon for XDB at CICS OS/2 start.
o CICS syncpoint at IMS TERM call or command
Software Requirements
=====================
To use Syncpoint Coordination support you must have one or more of the
following:
o IMS 2.5.00 or later
o XDB version 2.4 or later
o IBM DBM 1.2 or later.
Components
==========
This section lists the files that make up the Syncpoint Coordination
feature. Update installs them all in your CICS OS/2 system directory,
\CICS120\OS2DSD.
There are two new executable modules:
o MC2SYNC0.DLL Logic for Syncpoint Coordination
o MC2SYNC1.DLL INSTALLF and assembler subroutines
There are two sample modules to initialize and shutdown Syncpoint
Coordination, delivered in source code form:
o FAAOIS04.CCA
o FAAOISPT.CCA
These are replacements for the existing FAAOIS04.CCP and FAAOISPT.CCP
files. The extensions are changed so that the existing files are not
overwritten when you apply the update. This enables you to merge any code
of your own with the new modules.
Also supplied is a COBOL COPY file, MC2SYNCC.CPY. You need this to
compile FAAOIS04.CCA and FAAOISPT.CCA.
Using Syncpoint Coordination
============================
The Syncpoint Coordination feature must be enabled before you begin a
CICS OS/2 session. The code to initialize MC2SYNC0.DLL (syncpoint logic)
must be included in FAAOIS04.DLL. FAAOIS04.DLL executes at Program Load
Table Post Initialization (PLTPI) each time you start CICS OS/2. It is
provided by IBM as a facility for user initialization routines.
MC2SYNC0.DLL registers the entry-point SQLINIT and DBM entry-points
required to run .INT and .GNT applications using the associated database
products. Code added to FAAOISO4 for this purpose should not be carried
forward. Each time you close down CICS OS/2 you must also close down
MC2SYNC0.DLL. The code to do this goes into FAAOISPT.DLL.
Modules FAAOIS04 and FAAOISPT are supplied by IBM as customization
facilitities to enable the user to insert functions into CICS OS/2
startup and close down. FAAOIS04.DLL is executed, for each process, after
CICS OS/2 task initialization at startup. FAAOISPT.DLL is executed, for
each process, each time you close CICS OS/2 down.
The source code for these modules is in .CCP files. The .CCA files
provided with this update (see previous section) are intended as
replacements for the .CCP files. If you have added your own code to these
modules, you should merge it into .CCA files.
Then, follow the steps below:
1. Backup the existing FAAOIS04 and FAAOISPT .DLL and .CCP files.
2. Copy FAAOIS04.CCA to FAAOIS04.CCP, and FAAOISPT.CCA to FAA0ISPT.CCP.
3. Edit the code for DBM, XDB and IMS code in FAAOISPT.CCP to startup
and connect your database system the way you want. See the sections
Micro Focus IMSVS86 Support, IBM OS/2 Database Manager Support or XDB
Support. You can also turn off initialization for databases you do
not have connected. This avoids MC2SYNC0.DLL sending error messages
to the console.
4. Use CICS OS/2 Option translate, compile and link functions to
generate FAAOIS04.DLL and FAAOISPT.DLL from the .CCP files (see your
CICS OS/2 User Guide for details).
Micro Focus IMSVS86 Support
===========================
You have two choices for starting IMSVS86 with Syncpoint Control:
o Static Start
o Dynamic start.
These two start options are controlled in the CICS PLT module FAAOIS04. A
dynamic start loads the IMS support for the process but does not start
the database engine. The database engine is started on the first
application call to IMS. A static start loads the IMS support for the
CICS process and starts the database engine if it is not already started.
These two options (the static and dynamic start) are provided so you can
choose when the overhead of starting the IMS engine is incurred. If it is
possible that the IMS engine will never be used during an execution or if
it is important to have the CICS system available for non-IMS
transactions in advance of the IMS support, use a dynamic start. If
degraded performance on the first IMS transaction of an execution of CICS
is undesirable, then the use a static start.
The source code for IMSVS86 support in FAAOIS04.CCP looks like this:
* - IMS control
* set mc2-static-IMS-start to true
set mc2-dynamic-IMS-start to true
* set mc2-IMS-dormant to true
Comment out the lines you do not want to execute. Only one line should
be active. Set MC2-IMS-DORMANT to TRUE if you do not want MC2SYNC0.DLL to
start IMSVS86 at all.
IBM OS/2 Database Manager Support
=================================
The code in FAAOIS04.CCP for Database Manager control looks like this:
* - IBM DBM control
set mc2-support-DBM-restart to true
move 'SAMPLE' to mc2-sync-DBM-database-name
* set mc2-deferred-DBM-start to true
If you are not using DBM at all, remove the comment on the line to set
mc2-deferred-dbm-start.
Remove the ALIGN(2) directive from CICSOS2.DIR when compiling CICS OS/2
programs to work with DBM. DBM works to a system based on ALIGN(8) which
is the default. The ALIGN(2) directive can cause large unidentifiable SQL
codes to be returned due to an alignment mismatch between the
application and the DBM engine.
There are two ways to run CICS OS/2 with DBM.
Method 1 (Recommended):
-----------------------
Use this method when your programs all access the same database. Specify
the following options when checking programs that access the database.
Change the parameter for SQLDB to the name of your database (in the
example below it is shown as SAMPLE).
CBL XOPTS(COBOL2)
$set ans85
remove"id" vsc2
$set sql sqlaccess() sqlbind() sqldb(SAMPLE) nosqlpass
$set nosqlinit
Edit the code in FAAOIS04.CCP (shown at the start of this section) to
move the database name to mc2-sync-DBM-database-name. Comment out the
line which sets mc2-deferred-DBM-start to true.
If you get unexpected SQL errors at run-time which suggest that the
program is not bound, check that you have specified the database name
correctly.
Method 2:
---------
Use this method if different applications access different databases.
Use the same Checker options as in method 1 (see above), but specify:
$set sqlinit
instead of:
$set nosqlinit
In FAAOIS04.CCP, set MC2-DEFERRED-DBM-START to TRUE. Comment out the line
which supplies the database name.
The DBM is started on first DBM access and the requested database will be
connected. When an application runs requesting a different database the
Micro Focus support code disconnects from the previous database and
connects to the new one.
XDB Systems, Inc. Extended Database System Support
==================================================
The code in FAAOIS04.CCP for XDB control is shown below. If you are not
using XDB, set MC2-XDB-DORMANT to TRUE.
* - XDB control
* set mc2-activate-XDB to true
set mc2-XDB-dormant to true
set mc2-normal-XDB-start to true
* set mc2-foreground-XDB-only to true
* set mc2-background-XDB-only to true
Follow the steps below to use syncpoint control with XDB:
1. Do not use the LOGON, LOGOFF, or LOGOFFRUN directives when you check
or compile XDB programs.
2. Remove the ALIGN(2) directive from CICSOS2.DIR when compiling CICS
OS/2 programs to work with DBM. DBM works to a system based on
ALIGN(8) which is the default. The ALIGN(2) directive can cause large
unidentifiable SQL codes to be returned due to an alignment mismatch
between the application and the DBM engine.
3. Ensure that enough named pipes are configured to support at least all
the CICS OS/2 process (the number of foreground terminals plus
minimum number of free tasks). This is done by executing XDBSRVCO,
select (F5) Multi-user Configuration, select (F5) Named Pipes Option,
set the (F1) Named Pipes Interface to ON, and set the (F2) Named
Pipes threads to at least 4 or up to the maximum of 10.
4. Set mc2-activate-XDB to true to connect to XDB at CICS OS/2 startup.
Optionally you may also specify a user ID by adding to FAAOIS04.CCP
the statement:
move 'MYID' to mc2-sync-XDB-user-ID
You can limit XDB support to only CICS foreground or only CICS background
processes, reducing the XDB resources required. Set the flags
MC2-FOREGROUND-XDB-ONLY and MC2-BACKGROUND-XDB-ONLY as appropriate.
Foreground tasks are CICS terminals (for example V123 and V124), and
background are non terminal tasks (for example @03@).
Error Messages
==============
Error messages are delivered to the CICS OS/2 console via EXEC CICS WRITE
OPERATOR commands. The following error messages are currently
implemented:
MC20001I %1 database restarted successfully.
MC20002E %1 database start error. SQLCODE=%2
MC20003E Invalid syncpoint termination request.
MC20004E Invalid syncpoint initialize request.
MC20005E CICS OS/2 release level mismatch.
MC20006E Failed to address %1(%2). RC=%3
MC20007I CICS Syncpoint failed. EIBRESP=%1
MC20008E Failed to start Database Manager. RC=%1
MC20009E Failed to install exit processor. RC=%1
MC20010E Control request not START or STOP.
MC20011E XDB error message MC20012E XDB libraries not found.
MC20013E IMS failed to activate.
MC20014E IMS libraries not found.
Trace Entry Documentation
=========================
Trace entries are generated for start and stop of IMS, DBM and XDB,
connect to DBM databases, COMMIT and ROLLBACK, and messages above.
Messages use user trace ID 198 while the rest use trace ID 199. These
trace entries display in the trace file as UF198 and UF199.
CICS OS/2 OPTION EXECUTION CONTROL (MC2INIT)
============================================
Overview
========
This section should be regarded as an additional section to your CICS
OS/2 Option User Guide. It describes the CICS OS/2 Option Execution
Control (MC2INIT) feature which provides added control to CICS OS/2
startup, offering greater control over debugging and the run-time
environment.
The major benefits of MC2INIT are:
o Debug of more than one process or terminal at a time.
o Debug of PM, Dialog Manager, or Dialog System transactions.
o Color support for Animator.
o Individual configuration for any or all processes for a given
execution of CICS OS/2. You no longer have to reduce the number of
CICS OS/2 background tasks to one, in order to enable animation of
CICS tasks which run in background processes. Background processes
support non-facility tasks, printer tasks, and tasks attached to
future devices.
o VIO window for the operator interface to Animator.
o Use of other tools and debuggers such as Microsoft Source Profiler.
o Support for Xilerator
o Support for Microsoft CodeView and Source Profiler
o Support for any command line driven debugger or controlling tool
o A control screen size of greater than 25 lines for Animator, Advanced
Animator, and Xilerator.
o External user control of all run time switches. This also provides
greater consistency; CICS OS/2 as delivered from IBM starts processes
with different switches (-F or +F) depending on the type of process.
Components
==========
CICS OS/2 Option Execution Time Control (MC2INIT) consists of the
following new executable modules:
MC2INIT1.EXE
MC2INIT1.LBR
MC2INIT2.DLL
There is a replacement for an existing CICS OS/2 executable module:
FAAOMPML.EXA is a replacement for FAAOMPML.EXE
Before using Execution Time Control, take a backup of FAAOMPML.EXE and
then copy the new file, FAAOMPML.EXA to FAAOMPML.EXE.
There is also a sample configuration file:
MCO2.CFA
You can use this as a replacement for your current MCO2.CFG file. You
may want to include any changes you have made to MCO2.CFG in MCO2.CFA.
Then take a backup of MCO2.CFG, and copy MCO2.CFA to MCO2.CFG.
Using MC2INIT
=============
MC2INIT modifies CICS OS/2 startup procedures to provide greater control
over the start of debug sessions. This control is supplied through the
CICS OS/2 Option startup file, MCO2.CFG. A number of new tags have been
added to this file to provide individual control of CICS OS/2 tasks. A
sample file, named MCO2.CFA is included with this update (see previous
section).
We suggest you use MCO2.CFA as a replacement for your existing MCO2.CFG,
modifying it to suit your own needs. Read the rest of this document
carefully before making any changes to it.
The Workbench libraries must be available at startup along the path
defined by the COBDIR environment variable. The CICSWRK environment
variable must be set, and include the directory where the CICS OS/2 DLLs
are located. CICSWRK must also include the directory holding
MC2INIT1.EXE, MC2INIT2.DLL, and MCO2.CFG. MC2INIT1.LBR must be in the
same directory with MC2INIT1.EXE.
Errors are reported in a logfile in the CICS OS/2 system directory. The
log file name is MC2INIT.LOG. Exception conditions only are normally
placed in this file. For further information on a failure set the
environment variable MC2TRACE to any value (for example, SET MC2TRACE=Y).
The actual setting is irrelevant because MC2INIT only checks for the
presence of the variable. If the environment variable is present, the
startup module produces trace information to help with problem
determination and places it in MC2INIT.LOG. This information is
primarily intended for Micro Focus support personnel.
Configuration File
==================
The new tags for MCO2.CFG supported by MC2INIT are listed below. The
defaults supplied in MCO2.CFA are listed below each tag.
[MC2INIT1-ATTRIBUTES] Control Animator screen colors
;SYS-ATT-4: YELLOW ON RED Sets Animator menu key tops to red on
yellow. This line is commented out.
Remove the semicolon for it to take
effect. See your Workbench Reference for
information on colorizing screens.
[MC2INIT1-TRACE] Output trace messages for MC2INIT
OFF processes. Turned off by default.
[MC2INIT1-PROGRAMS] Libraries needed by Micro Focus tools
$CICSWRK\MC2INIT1.LBR This is the minimum needed in MCO2.CFG.
$COBDIR\CHECK.LBR
$COBDIR\UTILS.LBR
$COBDIR\COBCLI.LBR
$COBDIR\ADVANIM.LBR
$COBDIR\TOOLS.LBR
[MC2INIT1-SWITCHES] Sets run-time switches
(-F+K4) -F turns off numeric checking. +K4
causes RTS messages to remain on screen
until a key is pressed. Consult online
information on your COBOL system for
information about run-time switches.
;[MC2-CICS-@03@] Debugger control of background task
;ANIM @03@. Sets Animator as debugger for task
@03@. Commented out in supplied file.
;[MC2-CICS-@04@] Debugger control of background task
;ANIM @04@. Sets Animator as debugger for task
@04@. Commented out in supplied file.
[MC2-CICS-V124] Debugger control of foreground task @03@
ANIM Sets Animator as full-screen debugger
CONTROL:FULL SCREEN for terminal task V124.
Note that tags [MC2-CICS-xxxx] provide debugger control over any CICS
OS/2 task. Substitute the CICS OS/2 task name for xxxx. This tag accepts
the parameters documented in the next section, Process Control
Parameters. Naming tasks in MCO2.CFG not started by CICS OS/2 will not
cause an error.
The remainder of MCO2.CFA uses existing tags documented in your CICS
OS/2 Option User Guide.
They are set as below:
[MC-STARTUP]
APPLICATION-LIBRARY:MCO2.LBR
INITIALIZATION-LIBRARY:$COBDIR\TOOLS.LBR
[MC-TRACE]
OFF
[MC-PROGRAMS]
MCO2.LBR
$COBDIR\TOOLS.LBR
[MC-INSTALL]
$COBDIR\MFEXTMAP
[MC-PAINTER]
SCREENS
[MC-MENU]
CMENU
[MC-ONLINE]
/Q /Q
Note that [MC-ONLINE] is no longer used to determine which task runs
under a debugger.
Process Control Parameters
==========================
The session to be controlled by an entry is selected with the tag:
[MC2-CICS-xxxx], where xxxx is the process or terminal ID. For example,
[MC2-CICS-V123] selects terminal V123. Follow the tag with the process
control parameters.
These parameters are listed below. They are not case sensitive and can
be entered in upper, lower, or mixed case. The colon, :, is part of the
parameter and you must include it.
ANIM: Selects Animator for this process. Optionally, up to 75
characters of directives for Animator may follow (see the
COBOL Reference for details). The directive
"USER-SESSION" is noted if present and the process is
appropriately setup. Only one session system wide may
specify other than "CURRENT" (the default). The control
session may be either full screen or VIO windowed. The
default is for control to run from a VIO window. The
number of lines on the screen in the control session may
be controlled by the "LINES" parameter.
GANIM: Selects Xilerator for this process. Optionally, up to 75
characters of directives for Xilerator may follow. Do not
specify directives -P or -S. MC2INIT forces -P on and -S
off.
You can set the number of lines on the screen in the
control session with the "LINES" parameter (see below).
The control session is forced to be a full screen. The
target session will be in a PM session if that is the way
it is defined to CICS OS/2 or in a VIO window if it is
defined to CICS OS/2 as a full screen terminal.
CVP: Selects CodeView for this process. "EANIM" is also
accepted as an alias. Optionally, up to 75 characters of
directives for CodeView may follow. The control session
for CodeView is always started full screen.
PROFILER: Selects the Microsoft Source Profiler for this process.
Optionally, up to 75 characters of directives for
CodeView may follow.
NATIVE: Drops the Micro Focus enhancements for this process. The
only thing carried forward to the process is the run-time
switch settings (see the MC2INIT-SWITCHES tag in the
previous section).
Use NATIVE if you suspect that the MC2INIT enhancements
are causing a problem. NATIVE is not the default for a
process. The normal startup is to have the Micro Focus
Toolset Run Time Environment active without Animator.
ANYPGM: Selects the program or tool named in the parameter
"PROGRAM" (see below). The parameters supplied to this
program are given with this tag and may contain three
special variables (%1, %2, and %3). These special
variables are replaced at execution time as follows.
%1 This is the CICS OS/2 task control program
%2 This is the runtime SWITCHES passed to the CICS
OS/2 task control program.
%3 These are the startup variables expected by CICS
OS/2 task control on the command line.
If there are no parameters to pass to the PROGRAM other
than the CICS OS/2 startup information then this tag
should be coded "ANYPGM:%1 %2%3".
The following parameters are modifiers:
CONTROL: This specifies the type of session for the control screen
of Animator. It may specify "WINDOWED" (the default),
"PM-API", or "FULL-SCREEN". Note that some debuggers
(for example Xilerator and CodeView) override this
parameter and force "FULL-SCREEN".
LINES: This specifies the number of lines displayed on the
control screen for Animator, Advanced Animator, and
Xilerator. For Xilerator the lines parameter must be
acceptable to a full screen session for your system.
Acceptable parameters depend on your display hardware;
for VGA screens they include 25, 43 and 50
PROGRAM: This supplies the major parameter "ANYPGM" with the fully
qualified program-name of the controlling executable. It
will be this programs responsibility to start the CICS
OS/2 task control program and pass on the appropriate
switches and command line arguments.
Example MCO2.CFG Files
======================
This section contains some example sections from MCO2.CFG files, to show
you how to use the tags described in the previous section. They are
just segments of a configuration file.
Example 1:
----------
Start Animator on the background processes @03@ and @04@. This startup
defaults to each Animator session running in a VIO window and the CICS
process running in the same session as Animator. This precludes any "PM"
type applications from running on processes @03@ and @04@. This example
also changes the Animator key top color to yellow on red.
[MC2INIT1-ATTRIBUTES]
SYS-ATT-4: YELLOW ON RED
:
:
[MC2INIT1-SWITCHES]
(-F)
:
:
[MC2-CICS-@03@]
ANIM:
[MC2-CICS-@04@]
ANIM:
Example 2:
----------
Start Animator on terminal V123 and enable "PM" applications to run on
this terminal. Also enable numeric checking to screen the application
for invalid numeric fields.
[MC2INIT1-SWITCHES]
(+F)
:
:
[MC2-CICS-V123]
ANIM:USER-SESSION"PM"
CONTROL:WINDOWED
Example 3:
----------
Start Xilerator on V124. Set the control session to 50 lines to allow
more code to be viewed. Use mixed assembler and COBOL source display.
Control will be in a full screen session and the user session will be
"PM" if the original TCT entry for V124 was "PM" or else it will be a
VIO window (if the TCT specified full screen).
[MC2-CICS-V124]
GANIM:-M
Debugging PM-API Processes
==========================
You must be careful when debugging PM-API processes with Xilerator or
CodeView. Background or non-full screen 3270 processes are both PM-API.
If you use Ctrl-Esc while the debugger is at a breakpoint or in step
mode, OS/2 will hang and you will have to reboot the machine. This is
not a bug, but the nature of this type of debugging under OS/2.
To avoid this problem, it is suggested that at the first debugger stop
you do whatever debugging you can. Any attempt to switch sessions will
hang the machine. When you need to switch sessions, to provide input or
consult reference material, set a breakpoint you can trigger from
outside the debugger. Then "Zoom" the debugger, returning you to the PM
desktop.
You can now switch sessions. When you trigger the previously set
breakpoint, the debugger will reclaim the screen and keyboard focus
automatically. You can now only use the debugger until you enter "Zoom"
mode again.
Animator with USER-SESSION"PM" does not generally suffer from this
problem, and in many cases will be more friendly than Xilerator or
CodeView. However, if you are debugging code that is synchronous with
the PM message queue, the same rules apply. Most CICS OS/2 applications
do not fall into this category.
Restrictions In Related Software
================================
o Animator does not recognise the size of the screen if it is changed
after startup. This is a problem for starting Animator or Advanced
Animator for terminals that have screen sizes larger than 25 by 80
where USER-SESSION"PM" is not specified. Animator will detect the
screen size and then CICS OS/2 will re-size the screen for 3270
emulation of the larger terminal screen size. Animator will continue
to use the original session size.
To bypass this problem use the LINES parameter to set the session
size to the same size that the CICS OS/2 terminal uses. The session
will be resized prior to the start of Animator and when CICS OS/2
resizes the session it is effectively ignored.
o Only one cross session occurrence of Animator may be in the system at
a given time. This is a design limitation of Animator. The result is
that you can only work with one CICS process at a time if you require
PM (or Dialog System) support.
Error Messages
==============
This section lists MC2INIT error messages. They are displayed on the
screen for both VIO window and full screen sessions. They are also
written to the MC2INIT.LOG file, in the CICS OS/2 system directory.
o Start logic error.
This indicates an internal logic error.
o DosGetInfoSeg failed. RC=nnnn
The call to get operating system failed with the nonzero return code
nnnn.
o DosExecPgm failed. RC=nnnn
The operating system call failed with return code nnnn.
o DosStartSession failed. RC=nnnn
The operating system call failed with return code nnnn.
o Control statement error=nnnn
The CONTROL tag was coded but the parameter information was either
missing or invalid. The valid entries are coded either with or
without enclosing double quotes and include "PM", "FULL-SCREEN", and
"WINDOWED".
o No value for PROGRAM tag.
The PROGRAM tag was coded but there was no program-name supplied with
the tag.
o Unrecognized statement=xxxxxxxxx
Unrecognized control statement xxxxxxxxx was received. This indicates
an invalid tag.
o Screen re-size failed. RC=nnnn
The operating system call failed with return code nnnn. This may
indicate that the LINES parameter is not valid for the specified
session.
o Failed to find process for xxxxxxxxx
A search of the CICS OS/2 task control table failed to find the
process being started. This process may fail later because of CICS
OS/2 code using the wrong 3270 screen support code.
o CICS service level mismatch.
The CICS OS/2 task control table entry length does not match the
definition in this module.
o Failed to find CICS shared segment. RC=nnnn
The operating system call failed with return code nnnn. The call to
get the named shared segment containing the CICS OS/2 CSA failed.
o Invalid SWITCH syntax: xxxx
The SWITCH parameter xxxx is invalid. It must begin and end with "("
and ")" respectively and contain no embedded blanks.
PRODUCT CHECKLIST
=================
This delivery consists of one diskette, for applying an update to
CICS OS/2 version v2.5.04. This diskette will be 3.5 inch high density.
INSTALLATION
============
The update disk(s) contains a utility called UPDPROG, which you use for
applying the updates to your CICS OS/2 System. UPDPROG applies updates to
only one system directory, but it is likely that you have your system
spread across several directories. To cope with this, a batch file called
UPDATE is also supplied.
Provided you used Setup to install your CICS OS/2 System, you can use
UPDATE to apply the updates. UPDATE automatically applies the updates to
all the correct directories, calling Setup to establish the details and
then calling UPDPROG for each directory in turn. If you installed your
system manually, you will have to use UPDPROG yourself on each directory.
UPDATE also checks what versions you have of the CICS OS/2 system files,
to make sure you have 2.5.4 installed. If you have an earlier version
installed, UPDATE calls Setup to upgrade it to 2.5.4; Setup will ask you
to insert disks from your 2.5.4 set so it can do this.
To apply the update disk using UPDATE:
1. Place the diskette supplied in a disk drive, and make that drive
current. For example, if you use your A drive, enter at the prompt:
A: <Enter>
2. Start the update procedure by entering:
UPDATE <Enter>
3. UPDATE calls Setup, which displays an introductory screen. Read this
and then press <Enter> to get to the main menu.
4. On the main menu, select the option to start the update process
(instructions on the screen tell you how to select an option).
5. Setup displays the directory structure containing your CICS OS/2
System. You can change the directories by typing over them, but do
this only if the directory structure shown is wrong; do not put your
updates into different directories from your original system.
Normally you will simply press <Enter> at this screen to confirm it
is correct.
6. Setup now finishes (it may display "installation complete"), and
UPDATE calls Updprog.
7. Updprog checks the CICS OS/2 System files in the system directories
to see if any are from earlier versions than 2.5.4. If none are,
steps 8 through 10 are bypassed.
8. A list of the files that need to be reloaded from the 2.5.4 issue
disks to bring your system up to 2.5.4 is displayed, and you are
given the option of continuing or terminating. If your system
consists mainly of files from earlier than 2.5.4 you should
terminate, and install a 2.5.4 system before proceeding with the
update.
9. To prompt for the correct 2.5.4 disks, Updprog needs to know their
format. It assumes they are the same format as the update disk. If
this is not correct you can give their format by pressing one of the
following:
1 (for 5.25 inch low density diskettes)
2 (for 3.5 inch low density diskettes)
3 (for 5.25 inch high density diskettes)
4 (for 3.5 inch high density diskettes)
5 (for fixed disk)
You are asked to confirm your choice by entering Y. Entering N allows
you to select another format.
10. Updprog now starts copying files from your 2.5.4 disks; it asks you
for each disk as it needs it.
11. Setup now starts copying files from your updates disk(s); it asks you
for each disk as it needs it. First it looks for PKUNZIP.EXE in your
existing CICS OS/2 System; if it cannot find this file the most
likely reason is that you gave the wrong directory names. Messages
indicating which files are being updated are displayed.
12. When all the updates are complete, the files are rechecked to confirm
that they have been updated correctly, and UPDPROG finishes.
This completes the update process using UPDATE. If you installed your
2.5.4 system manually, you apply the update disk for each directory
individually using UPDPROG as follows:
1. Place the diskette supplied in a disk drive, and make that drive
current. For example, if you use your A drive, enter at the prompt:
A: <Enter>
2. Start the update procedure by entering:
UPDPROG <Enter>
3. You are asked to enter the name of the directory containing the CICS
OS/2 System you wish to update. To accept the default, which is
displayed with the prompt, just press <Enter>. Type the path-name of
that directory followed by <Enter>.
After this, the process is as from step 7 above.
Notes:
o If you install any files from 2.5.4 after applying this update, you
should reapply the update following the same procedure as above.
UPDPROG will indicate if no further changes are needed.
o When UPDPROG is reloading files, you may get a message of the form:
Unable to unzip or Unzip failed
(On OS/2 an error code will be given too.) The most likely
causes are that the disk is full or that the file already exists and
is read-only.
o If you are installing on a machine with a monochrome monitor, invoke
UPDATE with the /m option. For example, UPDATE /M.
o UPDATE will attempt to write to the disk containing the update disk
software. If it cannot do so because the disk is write protected,
then it will store its control files in the first directory on
COBDIR. It will also need the path set so that you can run CICS OS/2
System 2.5.4.
DISK CONTENTS
=============
High density 3.5 inch diskettes
-------------------------------
Disk 1
UDSETUP.EXE CICSUD.INI UPDPROG.@XE CHKDRV.EXE
UPDATE.CTL CHKSUMS.O2 UPDINFO.O2 CIC2UDRN.DOC
UPDATE.CMD UPDATE.BAT O2MASK.PCH IBMPTF29.DOC
MCO2.@FA CICSCOMP.@MD FAAOIS04.@CA FAAOISPT.@CA
MC2SYNCC.@PY FAAOMPML.@XA MC2INIT.@IP MC2SYNC.@IP
FAAAEWOF.@BL FAAECIW.@BL ECI.@OC DSDEMO.@IP
FAAAEFIE.T01 CICSRRDS.@MD FAASRPTR.@XE FAANBSIN.@LL
UPDDEL.EXE BTRCALLS.@LL FAAAEPDL.@LL FAAAEPEX.@LL
FAAAEPIM.@LL FAAAEPMN.@LL FAAANPIN.@LL FAAANPMC.@LL
FAAATPCI.@LL FAAATPDF.@LL FAAATPML.@LL FAAATSSH.@LL
FAAATSTR.@LL FAACEBR.@LL FAACICS.@LL FAACTPCM.@LL
FAACTPCN.@LL FAACTPDC.@LL FAACTPED.@LL FAACTPFC.@LL
FAACTPKB.@LL FAACTPPC.@LL FAACTPPP.@LL FAACTPSI.@LL
FAACTPSN.@LL FAACTPTA.@LL FAACTPTC.@LL FAACTPTS.@LL
FAADCALL.@LL FAAECPBE.@LL FAAHLPON.@LL FAAHLSON.@LL
FAAHPSPH.@LL FAALSPDL.@LL FAALSPFL.@LL FAALSPSF.@LL
FAALSPSG.@LL FAALSPSN.@LL FAALSPTC.@LL FAALSSSH.@LL
FAALSSUP.@LL FAAMGSON.@LL FAAMIR.@LL FAAMSPDM.@LL
FAAMSSO4.@LL FAAMSSOJ.@LL FAAMSSOP.@LL FAAMSSOT.@LL
FAANBSPH.@LL FAAO6SPH.@LL FAAO6STR.@LL FAAOIPTD.@LL
FAAOISET.@LL FAAOISII.@LL
Disk 2
FAAOISMM.@LL FAAOISQT.@LL FAAOISST.@LL FAAOISTT.@LL
FAAOMPSD.@LL FAAOMSLV.@LL FAAOTPED.@LL FAAOTPTK.@LL
FAAOTPTR.@LL FAAPLTSD.@LL FAASRSE1.@LL FAASRSE2.@LL
FAASRSML.@LL FAATCPCT.@LL FAAUTPSC.@LL FAAUTPUC.@LL
FAAUTSDM.@LL FAAANPCB.@XE FAACLPIN.@XE FAACPPML.@XE
FAAHLPOF.@XE FAAMSPTR.@XE FAAOMPML.@XE MCSTAR01.@XE
FAAOMPTR.@XE FAAOTPTK.@XE FAAOTXTK.@XE FAAPMPSM.@XE
FAAPRPML.@XE FAAUTPLC.@XE FAAHLFT1.PTR FAAHLFT2.PTR
FAAHLFT3.PTR FAAMGFMG.@TR ACCTSET.PMS FAADCMB.PMS
FAADCALL.PCP FAAPMPSM.PC FAACLIB.PIB FAAPMPSM.P
DFHAID.P FAACSTRT.P FAAECIH.P BMSSCRNS.PBR
MCO2.PXE MCO2.@BR MCCT01.PBL MCCT01.PCP
MCCT01.PNT MCCT01.PDY UPDATE.BAT UPDATE.CMD
=========================================================================
Micro Focus is a registered trademark of Micro Focus Limited.
Micro Focus COBOL Workbench, CICS OS/2 Option for Micro Focus COBOL
Workbench, Animator, Xilerator, and Dialog System are trademarks of Micro
Focus Limited.
XDB is a registered trademark of XDB Systems, Inc.
Microsoft, CodeView, and Source Profiler are registered trademarks of
Microsoft Corporation.
IBM is a registered trademark of International Business Machines
Corporation.
OS/2 and CICS OS/2 are trademarks of International Business Machines
Corporation.
IMSVS86 is a trademark of Stingray Software Company,Inc.
=========================================================================
Copyright (C) 1992-93 Micro Focus Ltd CIC2UDRN.DOC/2.5.16/16Dec93