Starting Your Product › How to Configure Without CA CSM › Other Initialization File Updates

Other Initialization File Updates

JCLLIB Member: ONLINE (or the online initialization file)

Installation Type: Both new and upgrade environments

If you want the interface to the full CA JCLCheck product, see the CA JCLCheck options data set and the JCLCHECK initialization file statement in the Systems Programming Guide for more information about enabling the interface. If you use the JCLCheck Common Component, ensure that the load library for that component is in the linklist or the STEPLIB concatenation for CA WA CA 7 Edition.

If you use the cross-platform scheduling features, see the XPDEF initialization statement to initialize the interfaces to CA WA Agents r11.3 or above, or to CA Unicenter Agents.

We recommend using the zIIP and Metrics options.

Note: For more information about these features and options, see the Interface Reference Guide and the Systems Programming Guide.

Copy your existing initialization file into the Version 12.0 JCLLIB library that you created previously, and modify it there.

Initialization file changes introduced in Version 12.0 include the following changes:

• RESIDENT statement

  This release supports another way to indicate that JCL library definitions using a symbolic index are loaded from the database at CA7ONL initialization. JCLDEFS=DATABASE is synonymous with JCLDEFS=VSAM.

• INIT statement

  METRICS={YES|NO} indicates whether to collect metrics data in the CA 7 log data sets. This data can be formatted using the SASSHIS8 report HR25.

  TYPE=MOVQ is obsolete in this version. If specified, it is treated as TYPE=ERST.

  ZIIP={NO|YES} indicates whether CA 7 routes work to a zIIP specialty processor.

• SECURITY statement

  With this version, you can segregate the SUBMIT and CALENDAR classes by CA 7 instance. Also, changes are introduced on a default user ID (possible exit elimination) and some BSUBCHK differences. CCLASS specifies the resource name that is used for the calendar accesses, while SCLASS indicates the resource name for the SUBMIT authority. To the SUBUID hierarchy, a DEFAULT specification is added, which indicates to use the DFLTUSR user ID in the JCL submitted.

• DAIO statement

  The SWFTRK/SCRTRK keywords are obsolete. An informational message is issued at startup when you specify the obsolete keywords.

• FORMAT statement

  The statement is obsolete because a CA Datacom/AD database replaces the VSAM database and queue data sets. An informational message is issued at startup when you include the obsolete statement in the initialization file.

• OPTIONS statement

  SUBSEL={NORM|ENH} indicates how submission selection, the selection of the next job to submit to the internal reader or to the cross-platform agent, is selected.

  • NORM indicates that subsystem selection operates as it did in previous releases. NORM is the default.
  • ENH (enhanced) indicates that queries are issued to the database to select the next job for submission. If using SUBSEL=ENH, know that selected WLB parameters are changed, removed, or both.

  If SHUTDOWN=Z4, Z5, or DMPQ is coded, replace it with an appropriate shutdown option unrelated to DMPQ.

Initialization file changes introduced in r11.3 include the following changes:

• SECURITY statement
  • AGCLASS= specifies the resource class name to use when performing agent job security calls. The default is FACILITY.
  • AGUSER= specifies a hierarchy of candidate user ID sources to determine the mainframe user (MFUser) to use for authorizing job submission for agent jobs.

    Note: If you validate agent jobs through external security, default values are used for AGCLASS and AGUSER when not explicitly coded on the SECURITY initialization statement.

  • LOGOPID=ALL indicates that transaction log records for all commands must include the operator ID. ALL includes type x'72' log records.
  • MULTIJOB=REQUEUE is valid when using the Parallel Submission Processing (PSP). This option requeues any jobs to the request queue with status MJOB if the job has more than one JOB statement.
• DBASE statement - The DEFAULTAG= keyword specifies the agent job mask to use for default values. The default is DEFAULTA.
• RESTART statement - The CONDCHK={NO|YES} specifies whether to synchronize the condition code checking between CA WA CA 7 Edition and CA WA Restart Option.
• CALENDAR statement - The PCALDSN= specifies the partitioned data set (PDS) name that contains perpetual calendar definitions.
• DAIO Statement -

  Increase the IOBS parameter, which states the number of I/O blocks for concurrent queue access, to at least 10, instead of 5, the previously recommended value. If you are executing OPTIONS PSP=Y, specify at least 5 more than the value specified in the OPTIONS MAXSUBOUT value. If you are executing PSP=Y and the IOBS parameter does not specify the correct number, CA WA CA 7 Edition corrects the number internally and issues message CA-7.890 - NUMBER OF QUEUE IOBS SET TO nnn.

• OPTIONS statement -
  • CPM=JFM indicates that the Critical Path Monitoring feature receives its job status information from Jobflow Monitor instead of CA WA CA 7 Edition itself.
  • CTIMSG={YES|NO} indicates whether to suppress extra messages that are generated during a CAICCI terminal usage. The messages include CA-7.XTM0, CA-7.SCMK, and CA-7.822.
  • JFM={NO|YES} indicates whether CA WA CA 7 Edition generates events that are sent to Jobflow Monitor to track the active and near-future workload.
• DRMODE statement -

  The TRIGGERS= keyword permits the specification of NONEXEC. This means that triggered jobs are marked as non-executable jobs if they are not in an active DRCLASS while in DRMODE.

• XPDEF statement -
  • AGENTJOB={NO|YES} indicates whether CA WA CA 7 Edition permits the definition, submission, and tracking of jobs that are sent to CA WA System Agents. This option, if set to yes, requires the CA IAS interface.
  • AGENTDAY=1-15 specifies the number of days to keep agent job information about the Agent VSAM file when the /DELAGNT command is executed. The default is 15 days.
• SMF statement - pertains to the processing of SMF data.
  • SMFXCF={NO|YES|xxxxxxxx} specifies whether to use XCF and can specify the XCF group name to assign to CA WA CA 7 Edition.
  • TZDISPLAY={EXEC|CA7} specifies the default option for those commands with a TZ (time zone normalization) keyword. The default is EXEC, which is the same as previous versions of CA WA CA 7 Edition.
  • TZPREDS={EXEC|CA7} specifies the time (CA WA CA 7 Edition or EXEC) used to satisfy initial requirements. The default is EXEC, which is the same as previous versions of CA WA CA 7 Edition.

  The CA WA CA 7 Edition SYSGEN process automatically defines an XCF checkpoint data set. If you intend to use XCF, add an XCFCKPT DD statement to your CA7ONL JCL at this time. See JCLLIB member CA07ONL as a sample. The data set must be formatted before use. You can format the XCF checkpoint data set as part of running job CA07N030 or individually by running job CA07N707.

• STATEMGR statement - controls the interface between CA WA CA 7 Edition and external system state monitors.
  • ARM={NO|YES} specifies whether CA WA CA 7 Edition registers with the IBM Automatic Restart Management (ARM). If ARM=YES is coded, an ARM policy must be defined in the couple data set.
  • OPSSSM={NO|YES} specifies whether CA WA CA 7 Edition interfaces with the System State Monitor of CA OPS/MVS EMA.
• UCC7VTAM statement –
  • The TCPTPORT specifies the TCP/IP port number on which CA WA CA 7 Edition listens for TCP/IP terminal commands. The keyword has no default.
  • The TCPTMOUT specifies a time-out value in seconds in which communications must be exchanged; the default is 10 seconds.

Starting with CA WA CA 7 Edition r11.1, the internalized cross-platform scheduling job (XPJOB) enhancement requires an internal cross-platform tracker (XTRK) task be active within the CA7ONL address space. As such, you no longer run XTRK as a started task or under ICOM. Running XTRK within CA WA CA 7 Edition and as a started task (or under ICOM) simultaneously leads to unpredictable results. We strongly recommend that you run XTRK within CA WA CA 7 Edition because it supports both XPJOBs and CA7TOUNI jobs.

Running XTRK within the CA7ONL address space requires the presence of the DD statement named XCKPT. You can use the current XTRK checkpoint file or can allocate a new XCKPT file using one of the following options:

• Use the CAL2JCL member AL2XPSCK to allocate the file.
• Edit the CA07N010 (the SYSGEN install macros sometimes override the prefix CA07) to include only the DDXCKPT DD statement.
• Use ISPF option 3.2. The attributes are RECFM=F, LRECL=BLKSIZE=4096. Allocate only two tracks.

Initialization file changes introduced in r11.1 include the following changes:

• DBASE statement - the DEFAULTXPJ= keyword specifies the XPJOB job mask to use for default values.
• SECURITY statement - the MIXPW= keyword specifies whether the logon password can validly contain lowercase characters.
• SVCNO statement - the cross-platform router and server options that are stated here can be overridden by the XPDEF statement when coded.
• XPDEF statement specifies the cross-platform environmental variables, including XPJOB submission, Monitor name, and High Availability Option (HAO) name.
• OPTIONS statement
  • CAL2C900= specifies the format of the CAL2C900I message.
  • GVARLVL= specifies the number of global variables nests.
  • GVARRPFX= specifies the default global reserved variable name prefix.
  • GVARSUB= specifies whether to use global variable substitution.
  • MAXSUBOUT= specifies the number of job submission output threads when PSP=Y.
  • PSP= specifies either parallel or serial job submission processing.

Initialization file changes introduced in r11 include the following changes:

• DRCLASS statements - disaster recovery classes that will be active if CA WA CA 7 Edition is started in disaster recovery mode.
• DRMODE statement - defaults settings for the new disaster recovery mode.
• EMAIL statement - support for the new email interface.
• JCL Statement - change INDEX=255 to reference the SMP/E-controlled target CAIHELP data set.
• OPTIONS statement
  • JCLTAG= allows for either literal CA-7 or the CA WA CA 7 Edition instance name to be inserted into the JCL comment statement that is inserted when a job is submitted to the internal reader by CA WA CA 7 Edition.
  • JSOP= keyword has two more options added: 2 and 3. These two new JSOP options control when to move jobs from the request queue to the ready queue and when to submit a ready queue job to the internal reader.
• SERVICEDESK statement - support for the new CA Service Desk interface.
• SVCNO statement - multiple instance support CA7= keyword replaces TEST= keyword, which can still be used.