APAR status
Closed as canceled.
Error description
In Chapter 3, Setting up a coordinating address space (CAS), in the section titled "Preparing to start a CAS", the sample CAS startup procedure in Figure 8 should be changed to match the EYUCAS member as distributed with the product: . //EYUCAS PROC SSID=CPSM, MVS/ESA Subsystem ID // XDM=N, Extended diagnostic mode // SPCF=N, SysPlex Coupling Facility // COLD=N, Cold start option // DUMP=ALL Capture all dumps //* //CPSMCAS EXEC PGM=BBM9ZA00, // PARM=('SSID=&SSID,XDM=&XDM,SPCF=&SPCF,COLD=&COLD', // 'DUMP=&DUMP'), // TIME=1440, // REGION=4096K //* //STEPLIB DD DISP=SHR,DSN=CPSM120.SEYUAUTH //BBACTDEF DD DISP=SHR,DSN=CPSM120.SEYUADEF //BBVDEF DD DISP=SHR,DSN=CPSM120.SEYUVDEF //BBIPARM DD DISP=SHR,DSN=CPSM120.EYUIPRM //BBSECURE DD DISP=SHR,DSN=CPSM120.SEYUPARM //* . In the same section, the syntax of the START command for a CAS should be changed to: . START procname ,SSID=ssid| ,XDM=Y!N| ,SPCF=Y!N| . - - ,COLD=Y!N| ,DUMP=Y!N!ALL| - --- . In the following list of parameter descriptions, add: . SPCF=Y!N - Indicates whether the sysplex coupling facility (SPCF) should be initialized. . Since CICSPlex SM does not make use of this CAS facility, you should specify SPCF=N, as provided in the distributed sample procedure. . In the same list of parameter descriptions, correct the DUMP= parameter (the distributed value is ALL, not than Y): . DUMP=Y!N!ALL --- Indicates whether system dumps (SDUMPs) are to be taken when the CAS subsystem recovery manager intercepts an unexpected abend. . When DUMP=ALL is in effect, an SDUMP is attempted for all unexpected abends. . If you specify DUMP=Y, the recovery manager attempts to take an SDUMP only when the failing function is running in supervisor state. If you specify DUMP=N, the recovery manager does not take an SDUMP for any abend, regardless of the PSW state at the time of the failure. . ----------------------------------------------------------- . In Chapter 4, Setting up a CICSPlex SM address space (CMAS), please change the description of the START= parameter in Table 6, CICS SIT parameters for a CMAS (page 71) to: . Parameter Explanation --------- ----------- START=(COLD,ALL) Cold start overriding other options. . The first time a CMAS is started, it should be cold started to install the necessary CICS resource definitions and establish CMAS-to-CMAS and CMAS-to-remote MAS connections. . Subsequently, a CMAS can be started with either START=COLD or START=AUTO. For more information, see "Restarting a CMAS." . ----------------------------------------------------------- . In Chapter 4, Setting up a CICSPlex SM address space (CMAS), please replace the section called "Restarting a CMAS" (page 73) with: . A CMAS that was shut down normally (using the CICSPlex SM SHUTDOWN action command) can usually be restarted with a SIT parameter of START=AUTO. However, you must specify START=COLD if you have: . - Modified any of the CICS resource definitions that are used by the CMAS. . - Added or removed CMAS-to-CMAS (CMTCMDEF) or CMAS-to-remote MAS (CMTPMDEF) connection definitions. . If a CMAS terminates abnormally (that is, through any means other than the CICSPlex SM SHUTDOWN action command), you must perform an emergency restart to allow CICS to perform backout processing. You can accomplish an emergency restart of a CMAS in one of two ways: . - If the CMAS is registered with the MVS/ESA automatic restart manager (ARM), an emergency restart occurs automatically. . - If the CMAS is not registered with ARM, specify START=AUTO in the CMAS startup procedure. . A CMAS should initialize and function properly after an emergency restart, provided you have made no changes to the CICS resource definitions or CICSPlex SM connection definitions. . If you have made any such changes since the last run of the CMAS (that is, the one that terminated abnormally), the CMAS may not function properly. In that case, you should shut down the CMAS using the CICSPlex SM SHUTDOWN action command and restart it, specifying START=COLD. For an illustration of the SHUTDOWN action command, see "Stopping a CMAS." . ----------------------------------------------------------- . In Chapter 13, Writing an API security exit, in the section called "Customizing the security routine" on page 190, add the following sentence to the end of the first paragraph (immediately following the section heading): . However, note that you cannot use the CICSPlex SM API from within EYU9XESV itself. . ----------------------------------------------------------- . In Chapter 15, Using CICSPlex SM tools for administering CASs, CMASs, and MASs, please add the following extra example to those listed on page 223: . . Example 6: To add a CICS system to a CICS system group associated with a monitor specification and to create the link between the CICS system and the monitor specification, you might specify: . CONTEXT EYUPLX01; CREATE CSGLCGCS GROUP(EYUCSG01) CICSNAME(EYUMAS1A); CREATE LNKSMSCS SPEC(MONSPC01) SYSTEM(EYUMAS1A); . When used to create a CICS system to CICS system group link record (CSGLCGCS) with the system group already associated with a specification, the batched repository update facility does not create a specification-to-CICS system link record (LNKSxSCS). To associate the CICS system with the specification, the LNKSxSCS record must be created explicitly. ----------------------------------------------------------- In Appendix D, CICSPlex SM system parameters, add a new column ("CICS Suspend Types") to Table 74, as follows (note also the slight change in the Suspend Class of DBCTRL to DBCTL): . CICS Value in Text in Suspend Class Suspend STALLxxx EYUPNNxxxx Types Parameters Messages ---------------------------------------------------------- . DBCTL DBCTL DBC DBCTRL DLI DLI DLI DLI Dispatcher DS_HELD DSP DISP Enqueue KC_ENQ ENQ ENQUEUE File FCxxxxxx FLE FILE Interval Control ICxxxxxx ITV INTV Journal JASUBTAS JNL JOURNAL JCxxxxxx Lock Manager LMQUEUE LCK LOCK Program Loader PROGRAM PGM PROGRAM Allocate Session ALLOCATE SES ALLCSESS IRLINK Storage xDSA STG STORAGE ExDSA Transient Data MBCB_xxx TDQ TSDATA MRCB_xxx TDEPLOCK TDIPLOCK TD_INIT Terminal Control ZCxxxxxx TRM TERM Task Wait EKCWAIT TSK TASKWAIT KCCOMPAT Temporary Storage TSxxxxxx TSQ TEMPSTOR Transaction Manager XM_HELD XMG TRANSACT XRF XRxxxxxx XRF XRF ----------------------------------------------------------- In Appendix D, CICSPlex SM system parameters, in the list of parameter descriptions that follow Table 73, CICSPlex SM parameters used in CMAS and MAS, please replace the description of the SEC parameter with the following (page 431): SEC(YES ! NO) -- Indicate whether the CMAS is to perform security checking of CICSPlex SM requests directed to the CICS systems it manages. If any of the CICS systems that a CMAS manages use the CICS/ESA system initialization table (SIT) parameter SEC=YES, then that CMAS must include the parameter SEC(YES) in EYUPARM. If you do not activate CICSPlex SM security in the CMAS, a connection cannot be established to a CICS system that specifies SEC=YES. If a connection is attempted, the following message is issued to the console, the CMAS job log, and the CMAS EYULOG: EYUCR0007E Security mismatch between CMAS cmasname and MAS masname. Connection terminating. ----------------------------------------------------------- . In Appendix D, CICSPlex SM system parameters, in Table 73, "CICSPlex SM parameters used in CMAS and MAS", please add the following parameters on page 428: . . Parameter CMAS Local MAS Remote MAS Default ---------------------------------------------------------- MASINITTIME n/a Optional Optional 10 . MASPLTWAIT n/a Optional n/a NO . . Also, in the list of parameter descriptions that follow Table 73, please add the following to the list of parameter descriptions on page 430: . . MASINITTIME(value ¦ 10) . -- . Specify the number of minutes, from 5 to 59, that CICSPlex SM should wait for the MAS to fully initialize. CICSPlex SM checks to see if the heartbeat task (COIE) is active. This indicates that the MAS is ready to process requests. If the heartbeat task is not active after the specified amount of time, CICSPlex SM shuts down the MAS agent (CICS continues to run). . . MASPLTWAIT(YES ¦ NO) . -- . For a local MAS running CICS/ESA 3.3 or later only. Indicate whether CICSPlex SM should suspend all CICS PLT processing until the MAS is fully initialized and connected to the CMAS. . ----------------------------------------------------------- In Appendix D, CICSPlex SM system parameters, in Table 73, "CICSPlex SM parameters used in CMAS and MAS", please add the following parameter on page 428: Parameter CMAS Local MAS Remote MAS Default ---------------------------------------------------------- COIRTASKPRI n/a Optional Optional 200 n/a for CICS for OS/2 Also, in the list of parameter descriptions that follow Table 73, please add the following to the list of parameter descriptions on page 430: COIRTASKPRI(value ! 200) --- Specify the task priority of COIR, in the range 0 to 255. COIR is a CICSPlex SM task that can be used to process evaluation definitions (EVALDEFs) independent of the MAS. For each EVALDEF that requests a separate task, an instance of COIR is started at the specified priority. If you specify a priority of 0, no separate COIR tasks are started; all EVALDEFs are processed by the MAS long-running task (LRT). ----------------------------------------------------------- . Additional Symptom(s) Search Keyword(s): 569508100 R120 R121 R122 R1DR HLR2120 JLR2121 JLR2122 VSE1DR SC330784-02 Also See II09227 and II10911 .
Local fix
CICSPlex SM Setup and Administration-Volume 1, SC33-0784-02 ----------------------------------------------------------- . In Appendix D, CICSPlex SM system parameters, in Table 73, "CICSPlex SM parameters used in CMAS and MAS", please add the following parameter on page 428: . . Parameter CMAS Local MAS Remote MAS Default
Problem summary
Problem conclusion
Temporary fix
Comments
WJB
APAR Information
APAR number
II09986
Reported component name
PB LIB INFO ITE
Reported component ID
INFOPBLIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1996-12-06
Closed date
1996-12-06
Last modified date
1997-11-11
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
11 November 1997