IBM Support

Updates to IMS Sysplex Manager V1R3 User’s Guide

Product Documentation


Abstract

Updates that apply to IMS Sysplex Manager V1R3 User’s Guide (SC19-2471-08).

Content

The most recent updates appear at the top of the list.



Update 1
Date of change: May 2018
Change description: Documentation changes for APARs PI75971, PI76820, and PI80700
Topics: Changes apply to multiple topics.

==================================

Topic: Viewing data > Viewing history data set information

A new topic, IMS command logging and auditing (GJEAUDIT), has been added for APAR PI75971. The following PDF contains the updated contents:


gjeuga38_APARPI75971.pdf

Note: Page, figure, table, and cross-reference numbers in this PDF extract might not match your current user guide version. Use this documentation extract for content update purposes only. Change bar markings on the left side of the page indicate the new or changed information. This information will be included in any future refreshes of the entire user guide.

==================================

Topic: Troubleshooting > Runtime messages (GJE)

New messages GJE8101W and GJE8102E have been added for APAR PI75971 as follows:



GJE8101W COMMAND AUDIT WARNING
REASON: x

Explanation: Command audit warning reason codes:
1: Empty history data set.
2: No commands are recorded in history within the date/timestamp range.

System action: Job ends with RC=04; no output data in the output file.

User response: Ensure the correct VSAM history file is used.




GJE8102E COMMAND AUDIT ERROR REASON: xxx

Explanation: Command audit reason codes:
11: GJEVSAM IDENTIFY error
12: GJEVSAM ACCESS or MAP error
16: GJEAUDIT Open error
17: SYSIN Open error
22: Data is before IMS Sysplex Manager version 1.3
32: GJESNAP Open error
40: HDSW block invalid
41: Exception block IMSID invalid
42: HDXW block invalid
43: Empty block should not be written
44: Other than 024 record in exception block
45: Invalid 024 VARDLL
46: Invalid 024 VARNUM
47: Invalid 024 Subrecord Length without LLZZ
101: MVS PARMS too long
102: Invalid adjust type
103: Invalid HHMM value DATE.... DESCRIPTION
110: GJEVSAM DD is not allocated
111: GJEAUDIT DD is not allocated
113: SYSIN DD is not allocated

System action: Job ends with RC=08. Processing stops.

User response:

  • For reason codes 11, 12, 32-47:
    Ensure the correct VSAM history file is used. Repeat the job with trace and send trace to IBM Software Support.
  • For reason code 16:
    Ensure the GJEAUDIT DD points to a valid file.
  • For reason code 17:
    Ensure the SYSIN points to a valid file.
  • For reason code 22:
    The VSAM history file is created with an older IMS Sysplex Manager release that does not support the enhanced auditing function. The enhanced auditing format and function is only appropriate for IMS Sysplex Manager V1.3 and higher.
  • For reason code 101:
    Correct the EXEC parameter and run the job again.
  • For reason codes 102-103:
    Correct the control input data in SYSIN DD and run the job again.
  • For reason code 110:
    Ensure the GJEVSAM DD is present and points to a valid file.
  • For reason code 111:
    Ensure the GJEAUDIT DD is present and points to a valid file.
  • For reason code 113:
    Ensure the SYSIN DD is present and points to a valid file.

==================================

Topic: Viewing data > Viewing IMS data > Viewing and managing destination queue depths

A note has been added to Step 3 in the Procedure section. This update is for APAR PI76820:
 

3. On the Destination Queue Depths panel (GJEP210), you can use the line commands s, d, and r to drill down further (these commands are valid only for CQS destinations). Line command s returns a list of messages and information on each message for the selected queue.

Note: IMS Sysplex Manager only supports up to 12K shared queue block size to be able to view messages.
Only the primary messages can be viewed.
In view mode, the message prefixes show. If the message data is larger than 4K, only the first 4K of message data displays, stating at the end that the "message continues...."
==================================
Topic: Configuring IMS Sysplex Manager > Configuration checklists

In the IMS control region section, under Table 1. “IMS control region configuration checklist,” the description for Step 3 has been changed. This update is for APAR PI80700.
 

Option 1: Create the GLX PROCLIB member (GLXEXIT0 or GLX iiii 0) to specify the
IMS Sysplex Manager logger exit (GJEIINT0).

Option 2: Configure IMS DFSDFxxx PROCLIB member (the SECTION=USER_EXITS
section with TYPE=LOGWRT) to specify the IMS Sysplex Manager logger exit
(GJEIINT0).

Note: If an IMS environment has both IMS DFSDFxxx PROCLIB member and the
Tools Base GLXEXIT0 PROCLIB member, the user exits in the Tools Base GLXEXIT0
PROCLIB member will not be processed.
==================================
Topic: Configuring IMS Sysplex Manager > Configuring the IMS control region

In the Procedure section, the description of the logger exit in Step 1 has been changed. This update is for APAR PI80700.

To configure the IMS control region, complete the following steps:
1. Configure the generic logger exit to point to the IMS Sysplex Manager logger exit. If you want to use the transaction affinity or the shared queue local buffer overflow protection, you must configure the generic MSC or QSN exits.

Logger exit
(Required) Option 1: Configure the GLX PROCLIB member (GLXEXIT0 or GLX iiii 0) to specify the IMS Sysplex Manager logger exit (GJEIINT0).

Option 2: Configure IMS DFSDFxxx PROCLIB member (the SECTION=USER_EXITS section with TYPE=LOGWRT) to specify the IMS Sysplex Manager logger exit (GJEIINT0).

Note: If an IMS environment has both IMS DFSDFxxx PROCLIB member and the Tools Base GLXEXIT0 PROCLIB member, the user
exits in the Tools Base GLXEXIT0 PROCLIB member will not be processed.

Publication Number

SC19-2471-08

[{"Line of Business":{"code":"","label":""},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX8AA","label":"IMS Sysplex Manager"},"ARM Category":[{"code":"","label":""}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"},{"Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SS5ELV","label":"IBM IMS Transaction Manager Solution Pack for z\/OS"},"ARM Category":[{"code":"a8m0z000000cvZdAAI","label":"IMS Transaction Manager Solution Pack for z\/OS"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.1.0"}]

Document Information

Modified date:
15 November 2020

UID

swg27051125