SysProg

Wednesday, March 18, 2020 12:11 PM

1.Cycling Regions
2.CICS DB2 Attachment
3.RMF - new SMF records?
4.Tools - Omegamon, SYSVIEW
5.Upgrade Considerations -
Job Changes - GMTRAN
Parm Changes: MEMLIMIT, Web change to Domain
Order of Services in Initialization
Exits
Catalog tables
Redefine and initialize the local and global catalogs
For each CICS region, you must delete, redefine, and initialize the DFHLCD and DFHGCD data sets:
• Delete your existing data sets.
• Define and initialize new local and global catalogs.
*Make sure that you use the DFHRMUTL and DFHCCUTL utility programs or the CICS-supplied JCL DFHDEFDS from your
target version of CICS TS.
• Start the CICS regions with an initial start, by using the START=INITIAL parameter.

Upgrade the CSD, you have two alternatives:

1. Upgrade the CICS-supplied definitions in your CSD to the latest level.
To do this upgrade, run the DFHCSDUP utility program with the UPGRADE command.
2. Define a new CSD by using DFHCSDUP INITIALIZE command.

New Cat-1 txn. Like purging DB2conn

PLTP/I Table changes
Creating PLEX CMAS maintenance points on each region

Order of services:
DFHPG
DFHXM
DFHDH
DFHTD

CEL4RTO has been replaced.

DFHDBMS has been replaced.
DFHEDFBR has been replaced.
DFHEITAB has been replaced.
DFHPLTMI has been added.
DFHPLTY4 has been added.
DFHXJCC has been added.
DFHXJCO has been added.
EDCXV has been added.
HHHAUTO has been added.
QLXFCREQ has been added.
QLXTDO2 has been added.
TJDUOUT has been added.
CEBR has been replaced.
CEDF has been replaced.
CEDX has been replaced.
CELR has been added.

CICS Page 1
 CELR has been added.
CPLT has been replaced.
DFHMQHC has been replaced.
DFHMQHE has been replaced.
DFHMQHK has been replaced.
DFHMQHU has been replaced.
DFHMQ1C has been replaced.
DFHMQ1E has been replaced.
CSQAVICM has been replaced.
CSQBCRMH has been replaced.

The CICS® transaction CLER allows you to display all the current Language Environment runtime options for a region, and
to modify a subset of these options. The CLER transaction can be used to:

• Display the current runtime options in effect for the region.

• Modify the following subset of the region runtime options:
○ ALL31(ON|OFF)
○ CBLPSHPOP(ON|OFF)
○ CHECK(ON|OFF)

○ The CLER transaction is conversational; it presents the user with commands for the terminal display.
The runtime options that can be modified with this transaction are only in effect for the duration of the running region.
○ The CLER transaction must be defined in the CICS CSD (CICS System Definition file). The following definitions are required,
and are in the Language Environment CEECCSD job in the SCEESAMP data set. Use the CEECCSD job to activate these
definitions, or you must define them dynamically with the CICS CEDA transaction.
From <https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ceea100/cler2.htm?view=embed >

OVERRIDE PARAMETERS FROM SYSIN:

APPLID=HHHS,SYSIDNT=HHHS,
AUTODST=NO,
GRPLIST=(CDFHLIST,HHHSLIST,CODLIST),
GMTRAN=CESN,
GMTEXT='PRODCICS FÖR SEB/TRYGG-HANSA',
INITPARM=(DFHD2INI='DB2B'),
INITPARM=(DFHDBCON='P0'),
DBCTLCON=NO,
DTRPGM=QLHDYPTH,
MQCONN=NO,
START=(AUTO,ALL),
TCT=NO,
XFCT=CITPFCT,
XTRAN=CITTTRN,
.END

+DFHSM0122I HHHS Limit of DSA storage below 16MB is 7,168K.

+DFHSM0123I HHHS Limit of DSA storage above 16MB is 120M.
+DFHSM0115I HHHS Storage protection is active.
+DFHSM0125I HHHS Transaction isolation is active.
+DFHSM0121I HHHS Reentrant programs will be loaded into read-only storage.
+DFHDM0101I HHHS CICS is initializing.
+DFHWB0109I HHHS Web domain initialization has started.
+DFHSO0100I HHHS Sockets domain initialization has started.
+DFHRX0100I HHHS RX domain initialization has started.

CICS Page 2
 +DFHRX0100I HHHS RX domain initialization has started.
+DFHMP0100I HHHS Managed platform domain initialization started.
+DFHLG0101I HHHS Log manager domain initialization has started.
+DFHEP0101I HHHS Event Processing domain initialization has started.
+DFHDH0100I HHHS Document domain initialization has started.
+DFHW20100I HHHS Web2.0 domain initialization has started.
+DFHXS1100I HHHS Security initialization has started.
+DFHSI1500 HHHS CICS startup is in progress for CICS Transaction Server Version
+DFHSI1501I HHHS Loading CICS nucleus.
+DFHXS1105 HHHS Resource profiles for class FCITPFCT have been built.
+DFHXS1105 HHHS Resource profiles for class MPÖP have been built.
+DFHDU0304I HHHS Transaction Dump Data set DFHDMPA opened.
+DFHXS1105 HHHS Resource profiles for class TCITTTRN have been built.
+DFHXS1103I HHHS Default security for userid YCICSP has been established.
+DFHSI1600I HHHS VTAM High Performance Option is active.
+DFHCQ0100I HHHS Console queue initialization has started.
+DFHCQ0101I HHHS Console queue initialization has ended.
+DFHCQ0103I HHHS MVS console queue is open.

+DFHSI8430I HHHS About to link to PLT programs during the third stage of initia
+BMC202810E RUV Internal error. NTS was not found, RC(00000004).
+IDI0172I Fault Analyzer NameToken anchor built at 2A985148 by TCB 9C3E88.
+IDI0071I Install of program IDIXCX53 exit XPCABND completed successfully.
+IDI0071I Install of program IDIXCX53 exit XDUREQ completed successfully.
+IDI0071I Install of program IDIXDSCR completed successfully.
+DFHSI8434I HHHS Control returned from PLT programs during the third stage of i

Catalog Redefinition
Before the local catalog can be used to start a CICS® region, you must initialize it with
• data from the domain manager parameter records and
• three loader domain parameter records.
About this task
The domain manager parameter records contain information relating to the CICS domains and are identified by their
domain names.
The three loader domain parameter records contain information relating to these resources:
• DFHDMP, the CSD file manager
• DFHEITSP, the RDO language definition table
• DFHPUP, the CSD parameter utility program

<https://www.ibm.com/support/knowledgecenter/SSGMCP_5.5.0/configuring/cics/dfha2_initializing_localcat.html?
view=embed>

You usually specify the system initialization parameters that CICS® is to use in the following ways, before
starting CICS.
Procedure
• In the system initialization table, loaded from a library in the STEPLIB concatenation of the CICS startup
procedure
• In the PARM parameter of the EXEC PGM=DFHSIP statement of the CICS startup procedure
• In the SYSIN data set defined in the startup procedure, but only if SYSIN is coded in the PARM parameter.
Results
The system initialization parameters are processed in the order outlined above, with later system initialization parameter
values overriding those specified earlier.

CICS Page 3
 values overriding those specified earlier.
Example
For example, if your CICS startup procedure specifies:
//INITCICS EXEC PGM=DFHSIP,REGION=&REG,
// PARM=('SYSIDNT=HTH1,SIT=6$,SYSIN,CN')
//*
//SYSIN DD DISP=SHR,DSN=&libpfx..CICSH###.SYSIN(CICS&CLONE)

CICS uses system initialization parameters from the following sources, with later system initialization parameters
overriding earlier ones:
3. The system initialization table, DFHSIT6$, from the STEPLIB concatenation.
4. The member CICSH### of the CICSTS55.CICS.CICSH###.SYSIN data set.
5. The system console.

From <https://www.ibm.com/support/knowledgecenter/SSGMCP_5.5.0/configuring/cics/dfha602.html?view=embed>

The authorized cross-memory (AXM) server environment provides the runtime environment for CICS data
sharing server regions. You must define and start AXM system services to run any of the CICS data sharing
servers.
About this task
To establish AXM cross-memory connections for an MVS image, you must define an MVS subsystem called AXM.
You can choose to create the subsystem statically or dynamically.

From <https://www.ibm.com/support/knowledgecenter/SSGMCP_5.3.0/com.ibm.cics.ts.sysdefinition.doc/topics/dfha2
_axm_system_services.html?view=embed>

Coupling facility data tables (CFDTs) provide a method of file data sharing, using CICS® file control, without the need for a
file-owning region, and without the need for VSAM RLS support.
CICS CFDT support provides rapid sharing of working data within a sysplex, with update integrity.

From <https://www.ibm.com/support/knowledgecenter/SSGMCP_5.3.0/com.ibm.cics.ts.sysdefinition.doc/topics/dfha2
_coupling_facility_datatables.html?view=embed>

A journal record can be written under these circumstances:

• A definition in the data repository is added, removed, or updated.
• An operations action is issued against a MAS.
• A real-time analysis event is generated.

<https://www.ibm.com/support/knowledgecenter/SSGMCP5.2.0/com.ibm.cics.ts.installation.doc/topics/dfha1hr.html?
view=embed>

If you do not want to use the default log stream name of EYUJRNL,
define a JOURNALMODEL resource in the CSD that has the desired log stream name.
• To make the JOURNALMODEL resource definition available during CMAS initialization, include the JOURNALMODEL
resource definition in a CSD group list.
Include this group list in your CMAS startup using the system initialization GRPLIST parameter.
• To add the JOURNALMODEL resource to the CSD, either edit and run the JCL contained in sample
member CICSTS52.CPSM.SEYUSAMP(EYUJRNE$) to run batch utility DFHCSDUP or use the CICS CEDA transaction.
• You must also update the CICS system initialization parameters used to start the CMAS by setting the GRPLIST parameter
to reference the new group list.

You can shut down a CMAS using the WUI shutdown action button or the COSD transaction.
You can use the CMASSTOP command of the CODB system-level debugging transaction to shut down the CMAS, but
CODB is restricted and must be used only at the request of IBM® customer support personnel.
CICS Page 4
 CODB is restricted and must be used only at the request of IBM® customer support personnel.

Do not attempt to shut down a CMAS in these ways:

• Issue the CEMT PERFORM SHUTDOWN command against a CMAS
• Cancel the CMAS job from MVS™
If you take either of these actions, the CMAS cannot shut itself down properly.

• If you shut down more than one CMAS at the same time, you might receive message EYUCP0205S.
• In this situation, the message does not indicate a problem, and CICSPlex® SM does not produce a diagnostic SVC dump as
it normally would when this message is issued.
• You can avoid the message by staggering your CMAS shutdowns.

Problem
You receive one or more of the following message during CMAS shutdown:
EYUWM0403E Workload Manager Task has reported an error processing event ( PI Interval )
Cause
Shutting down the CMAS using CEMT PERFORM SHUTDOWN command.
https://www.ibm.com/support/pages/eyuwm0403e-workload-manager-task-reported-error-processing-event-pi-interval

CICS makes the decision(HOT/WARM) by inspecting two records in the global catalog:
the recovery manager control record, and the recovery manager autostart override record.

• EYUCMSSP – CICS system initialization overrides for a CMAS.

• EYUCMS0P – EYUPARM parameters for a CMAS.
• EYUCMASP – starts a CMAS.
• EYUCMASJ – JCL to start a CMAS. It runs EYUCMASP.

CMF(CICS MONITORING FACILITY) WRITES SMF type 110 records

OMEGAMON for CICS writes this data as SMF type 112 records.
System Logger data writes SMF type 88 can help an installation avoid STRUCTURE FULL exception.
To dump the SMF data set, use the SMF dump program (IFASMFDP).

PTF Info:
PROBLEM DESCRIPTION: A compatibility APAR is required to *
* tolerate private program and library changes the **
* format of the CRESLIBR and CRESPRGM records, *
* which are written to the EYUDREP file. To *
* ensure that the changed format of the *
* records does not clash with the previous *
* format of the records the EYU9XDUT utility must be run against the *
* CMAS's EYUDREP, specifying the current *
* version as the target version parameter *
* (i.e, PARM=('TARGETVER=0410') if the current *
* release is CPSM V4R1M0 or *
* PARM=('TARGETVER=0420') if the current *
* release is CPSM V4R2M0), with STEPLIB *
* pointing to the SEYUAUTH library updated by *
* applying or backing off the PTF. This will *
* insure that all CRESxxxx records will be *
* removed from the EYUDREP file. *

In a warm restart, CICS uses the installed resource definitions saved in the CICS global catalog at warm shutdown, and

CICS Page 5
In a warm restart, CICS uses the installed resource definitions saved in the CICS global catalog at warm shutdown, and
therefore the CSD, FCT, and GRPLIST parameters are ignored. (At CICS startup, you can only modify installed resource
definitions, including file control table entries, or change to a new FCT, by performing a cold start of CICS with
START=COLD.)
From <https://www.ibm.com/support/knowledgecenter/SSGMCP_5.5.0/reference/sit/dfha2_newsit.html?view=embed >

Restrictions
You can specify the NEWSIT parameter in PARM, SYSIN, or CONSOLE only.
From <https://www.ibm.com/support/knowledgecenter/SSGMCP_5.5.0/reference/sit/dfha2_newsit.html?view=embed >

The MXT system initialization parameter specifies the maximum number, in the range 10 through 2000, of user tasks that
can exist in a CICS® system at the same time. The MXT value does not include CICS system tasks.
MXT={250|number}
From <https://www.ibm.com/support/knowledgecenter/SSGMCP_5.5.0/reference/sit/dfha2_mxt.html?view=embed >

The OFFSITE system initialization parameter specifies whether CICS® is to restart in off-site recovery mode; that is, a
restart is taking place at a remote site.
OFFSITE={NO|YES}
For a successful off-site restart, the log records of the failed CICS region must be available at the remote site. CICS
does not provide a facility for shipping log records to a remote backup site, but you can use a suitable vendor product
to perform this function
From <https://www.ibm.com/support/knowledgecenter/SSGMCP_5.5.0/reference/sit/dfha2_offsite.html?view=embed >

If the rule action defined is <event>:

• Check that event processing is started. DFHMP3011 message in the CICS log indicates if policy events are being lost
because event processing is stopped. • Check that the adapter or adapterset is installed. DFHMP3004, DFHMP3005 or
DFHMP3006 messages in the CICS log indicate which artifacts might be missing.

Problem
You are installing a local file definition and receive message DFHAM4803. The message indicates the install failed because
the deletion of an existing definition failed. However, you are unable to find a duplicate definition within a File Control
Table (FCT) or as a Resource Definition Online (RDO) definition.
Symptom
DFHAM4803 Install failed because an existing definition for file filename could not be deleted.
Cause
A file definition named ABCD was found that included options REMOTESYSTEM=SYSID and REMOTENAME=ABCD.
However, SYSID was coded equal to a region that had file ABCD defined as local. This caused the remote file to be
installed as a local file and message DFHAM4803 to be issued validly due to a duplicate definition. In this case, it was
found that the SYSID had been entered as a typo.
Resolving The Problem
Fix the remote file definition so that it is no longer defined with a REMOTESYSTEM equal to a SYSID of a region that has
the file defined locally.
From <https://www.ibm.com/support/pages/dfham4803-during-install-local-file-definition>

CICS will record the status of a CICS region to the DFHRSTAT CFDT file.
The definition for this file is automatically generated when the CICS region status function is initialized.
The CICS file definition will be related to a physical CFDT that’s named after the CICSplex name the region belongs to.
When defining this file, RS domain will also generate a poolname gathered from the CICSplex Definition (CPLEXDEF) the
starting region belongs to. The default poolname is also DFHRSTAT. In any given z/OS image, there must be one region
status server per poolname running in that image.
From <http://enterprisesystemsmedia.com/article/cics-sysplex-optimized-workload-routing/4#sr=g&m=o&cp=or&ct=-tmc&st=(opu%20qspwjefe)&ts=1586249052>

CICS Page 6
 Order of Installation Jobs:
• Running the DFHIHFS0 job
This job create a file system and cicsts directory.
• Running the DFHIHFS1 job
This job unmounts and deletes the file system, before creating and mounting a new file system as specified in DFHISTAR.
• Running the DFHISMKD job
This job creates the UNIX System Services directories.
• Running the DFHINST1 job
This job allocates and catalogs CICS Transaction Server distribution and target libraries.
• Running the DFHINST2 job
This job allocates the CICS Transaction Server RELFILE data sets. If you run the DFHINST2 job now, you ensure that enough
space has been allocated to the RELFILE data sets to allow the DFHINST5 job to complete.
• Running the DFHINST3 job
This job allocates the CICS Transaction Server SMP/E data sets.
• Running the DFHINST4 job
This job primes the global zone, target zone, and distribution zone, which are the new SMP/E zones created in DFHINST3..
• Running the DFHINST5 job
This job uses the RECEIVE command to receive the CICS Transaction Server software from the distribution tape into the
RELFILE data sets created by the DFHINST2 job. This installation job, apart from the initial IEBCOPY job, is the only job tha t
requires the distribution tape to be mounted.
• Running the DFHINST6 job
This job performs the SMP/E APPLY and ACCEPT functions that install CICS Transaction Server into the target and
distribution libraries respectively.
• Running the DFHIJVMJ job
The DFHIJVMJ job creates the customized sample JVM profiles that you require if you want to run a JVM program in CICS.
• Running the DFHCSVCJ job
The DFHCSVCU utility program dynamically updates the MVS SVC number specified in the PARM statement to invoke the
required module, and so removes the need to restart the z/OS LPAR in order to use a new or updated SVC.
From <https://www.ibm.com/support/knowledgecenter/no/SSGMCP_5.2.0/com.ibm.cics.ts.installation.doc/topics/dfha1q5.html?view=embed >

MQADMIN:
If IBM MQ objects are defined in CSQINP2, IBM MQ attempts to redefine them each time the queue manager is started. If
the objects already exist, the attempt to define them fails. If you need to define your objects in CSQINP2, you can avoid
this problem by using the REPLACE parameter of the DEFINE commands, however, this overrides any changes that were
made during the previous run of the queue manager.
From <https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.adm.doc/q022120_.htm?view=embed >

The data conversion exit utility

The IBM MQ for z/OS data conversion exit utility ( CSQUCVX ) runs as a stand-alone utility to create data conversion exit
routines.
The change log inventory utility
The IBM MQ for z/OS change log inventory utility program ( CSQJU003 ) runs as a stand-alone utility to change the
bootstrap data set (BSDS). You can use the utility to perform the following functions:
• Add or delete active or archive log data sets.
• Supply passwords for archive logs.
The print log map utility
The IBM MQ for z/OS print log map utility program ( CSQJU004 ) runs as a stand-alone utility to list the following
information:
• Log data set name and log RBA association for both copies of all active and archive log data sets. If dual logging is not
active, there is only one copy of the data sets.
Active log data sets available for new log data.
CICS Page 7
• Active log data sets available for new log data.
• Contents of the queue of checkpoint records in the bootstrap data set (BSDS).
• Contents of the archive log command history record.
• System and utility time stamps.
The log print utility
The log print utility program ( CSQ1LOGP ) is run as a stand-alone utility. You can run the utility specifying:
• A bootstrap data set (BSDS)
• Active logs (with no BSDS)
• Archive logs (with no BSDS)
The queue sharing group utility
The queue sharing group utility program ( CSQ5PQSG ) runs as a stand-alone utility to set up Db2 tables and perform
other Db2 tasks required for queue sharing groups.
The active log preformat utility
The active log preformat utility ( CSQJUFMT ) formats active log data sets before they are used by a queue manager.
If the active log data sets are preformatted by the utility, log write performance is improved on the queue manager's first
pass through the active logs.
The dead-letter queue handler utility CSQUDLQH
runs as a stand-alone utility. It checks messages that are on the dead-letter queue and processes them according to a set
of rules that you supply to the utility.
• CSQUTIL utility for IBM MQ for z/OS
The CSQUTIL utility program is provided with IBM MQ for z/OS to help you perform backup, restoration, and
reorganization tasks, and to issue commands and process object definitions.

Setting system parameters

In IBM MQ for z/OS, a system parameter module controls the logging, archiving, tracing, and connection environments
that IBM MQ uses in its operation. The system parameters are specified by three assembler macros, as follows:
CSQ6SYSP
System parameters, including setting the connection and tracing environment.
CSQ6LOGP
Logging parameters.
CSQ6ARVP
Log archive parameters.
From <https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.pro.doc/q004070_.htm?view=embed >

V3.2 to 4.2
Use TSMAINLIMIT instead of EDSALIM

From <https://www.ibm.com/support/knowledgecenter/SSGMCP_4.2.0/com.ibm.cics.ts.migration.doc/topics/dfhe5_sip_new.html?view=embed >

CICS Page 8