Administrative and Operational Enhancements › CA Culprit for CA IDMS Enhancements › Report Separation

Report Separation

In z/OS, you can now separate reports from other output generated by Culprit, such as diagnostic messages, by using the new Output DDNAME Override profile option. This option changes the DDNAME used for the report output when using one-step JCL. You can use this option to segregate the report output from the listings and diagnostic messages.

Sample one-step JCL is shown next:

OUTDD=(ddname,00,’’,00)

Output DDNAME Override Option

The new OUTDD profile option specifies the DDNAME used for report output when using one-step JCL.

DDNAME Syntax

The following syntax shows the new OUTDD profile option.

►►─── OUTDD=(ddname,00,’’,00) ──────────────────────────────────────────────►◄

DDNAME Parameter

This section describes the Output DDNAME Override option parameter.

OUTDD=(ddname,00,’’,00)

Specifies the DDNAME to which CULE writes report output when using one-step JCL.

Default: SYS004

All reports in the same Culprit run are written to the file identified by ddname unless you specify a special file-type indicator (PS, IS, or NS) on the report’s output card.

Note: If you specify this parameter, a new DD statement must be added to the execution JCL that describes the file. The DD statement must specify the file’s block size; otherwise, the job will abend with an s013.

CA OPS/MVS Integration for z/OS

CA IDMS provides internal communications with the CA OPS/MVS Application Program Interface (API), employing START/UP/STOP/DOWN state notifications, heartbeats, and passes specific messages into the OPSLOG facility. This helps ease the automation of the production copies of CA IDMS.

State Reporting

CA IDMS reports its current state information to the System State Manager (SSM) component of CA OPS/MVS via the OPS/MVS generic event API. This state can be forwarded to other Common Service components such as the MM Status Monitor. CA OPS/MVS generates these messages into the JES log whenever the status of the CA IDMS system changes, as in the following example:

OPSQNOTIFY CASTATE API received for <jobname> with STARTING , Version R18.0 and Level BAT  nnn a=008E
OPO1370H <jobname> X'0000' X'0000' X'0200' NONE  300 OPSLOGSV   CASTATE <jobname> applid:CAIDMS version:R18.0 level:BAT  nnn

OPSQNOTIFY CASTATE API received for <jobname> with UP , Version R18.0 and Level BAT  nnn a=008E
OPO1370H <jobname> X'0000' X'0000' X'0200' NONE  300 OPSLOGSV   CASTATE <jobname> applid:CAIDMS version:R18.0 level:BAT  nnn

OPSQNOTIFY CASTATE API received for <jobname> with STOPPING , Version R18.0 and Level BAT  nnn a=008E
OPO1370H <jobname> X'0000' X'0000' X'0200' NONE  300 OPSLOGSV   CASTATE <jobname> applid:CAIDMS version:R18.0 level:BAT  nnn

OPSQNOTIFY CASTATE API received for <jobname> with DOWN , Version R18.0 and Level BAT  nnn a=008E
OPO1370H <jobname> X'0000' X'0000' X'0200' NONE  300 OPSLOGSV   CASTATE <jobname> applid:CAIDMS version:R18.0 level:BAT  nnn

The CA OPS/MVS OPSVIEW facility is able to manage and display System State Manager resources and its states:

SSM Resource Status----------- CA31 -- O P S V I E W --------- Row 1 to 5 of 5
 Date/Time: 2010/08/03 11:50                       Filtered: N   View ===> ALL  
 System: *        SSM Mode: ACTIVE   Version: 2                  Wait ===> 10   
                                States              Modes                       
 Cm Sta Resource Name      Current  Desired  Res Pre Ref Tng Action   Message   
 -- --- ------------------ -------- -------- --- --- --- --- -------- ----------
 __     SYSTEM71           DOWN     UP        A   A   A   N  ACTIVE             
 __     SYSTEM72           UP       UP        A   A   A   N  ACTIVE             
 __     SYSTEM73           STARTING UP        A   A   A   N  ACTIVE             
 __     SYSTEM74           STOPPING UP        A   A   A   N  ACTIVE             
 ******************************* Bottom of data ********************************
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
 Command ===> ________________________________________________ Scroll ===> CSR 
  F1=Help      F2=Split     F3=Exit      F4=Return    F7=Up        F8=Down      
  F9=Swap     F10=Tleft    F11=Tright   F12=Retrieve

Heartbeats

Heartbeats are used by applications to report that they are alive, their current processing status, and the reason for that status. This status can be forwarded to other Common Service components such as the MM Status Monitor and the Alert Monitor. CA IDMS currently reports a NORMAL status to indicate that the IDMS system is alive every five seconds. CA OPS/MVS generates messages whenever a change in status is detected, as follows:

OPO1370H <jobname> X'0000' X'0000' X'0200' NONE  300 OPSONOTIFY CAHEARTBT received for <jobname>  applid:CAIDMS version:R18.0
OPSONOTIFY CAHEARTBT received for <jobname>  applid:CAIDMS version:R18.0 level:BAT  nnn status:NORMAL reason:ACTIVE

Heartbeat messages only appear in the log when there is a change. For example, when a product is no longer communicating a NORMAL state or no longer communicating at the expected interval. Likewise, when a problem does occur, the error is only reported in the log once. No other messages are received until the heart beats have been resumed.

Message Handling

CA IDMS employs OPS/MVS API calls to pass log, trace, and journal dump requests into OPS/MVS OPSLOG and to the OPS/MVS rules engine. CA IDMS currently pass these messages into OPSLOG:

• DC050001 – Log % full message?
• DC050004 – Log is FULL message?
• DC205003 – Journal message?
• DC050024 – TRC % FULL message?
• DC050027 – TRC is FULL message?

If any of these messages are encountered, an OPS/MVS API event is generated. You can then write your own API rule to take a specific action. See the Appendix Sample OPS/MVS API rule for a working example.

CA IDMS passes the event name to the OPS/MVS rules engine based on following rules:

CAIDMSxxxn

xxx can be

• LOG for DC050001,DC050004 messages
• JNL for DC205003 messages
• TRC for DC050024,DC050027 messages

n can be:

• A numeric value in range of 0 – 9 which means the LOG/TRC is 0 – 99% full in 10% increments, e.g. CAIDMSLOG8 means an event has been generated that the log is about 80% - 89% full.
• A “F” letter which means the log or TRC is full. For example CAIDMSTRCF.

Implementation CA OPS/MVS API rules

CA OPS/MVS Automated Operations Facility (AOF) can take an action in response to various types of system events. CA IDMS exploits API events to enable easy implementation of AOF rules which permit automation of the production copies of CA IDMS.

Notes:

• For information on how to implement CA OPS/MVS rules, refer to the CA OPS/MVS® Event Management and Automation - AOF Rules User Guide.
• For information on how to automate the offloading / archiving processes for DC log, DC traces and journals on CA IDMS, see the Appendix Sample OPS/MVS API rule.