IBM Support

Updates to IMS High Performance System Generation Tools V2.4 User's Guide (SC27-9501-00)

Product Documentation


Abstract

Updates that apply to IMS High Performance System Generation Tools V2.4 User's Guide (SC27-9501-00).

Content

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


Update 2

Date of change: June 2019

Change description: Documentation changes for APAR PH11959

Topics: Changes apply to multiple topics.

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

Topic: Resource update list > Editing a resource update list > Updating an AGN definition > Reloading an ACBLIB member

This topic and its subtopics have been moved so that this topic is on the same level as the "Updating an AGN definition" topic.

The new structure looks like this:

Resource update list

Managing a resource update list    

Editing a resource update list

...

Updating an AGN definition

Reloading an ACBLIB member

Reloading an ACBLIB member by using HP Sysgen ACB reload

...

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

Topic: Resource update list > Editing a resource update list > Updating an AGN definition > Reloading an ACBLIB member > Reloading an ACBLIB member by using IMS member level global online change

The WAIT parameter description has been appended to Step 3 as the last paragraph.

3. Copy the updated ACB member to the staging ACBLIB, and install the resource update list to reload the ACBLIB member specified in the resource update list.

...

For information about CSLOMCMD request return and reason codes, see IMS System Programming APIs. For return and reason codes associated with commands in messages IOH4725E through IOH4728E, see IMS Commands.

image-20181126113638-1If you specify Y for the PSB's field, message CSLN030W might be returned. This means that the IMS command was timed out. You can avoid a time out by using the WAIT parameter. For details about the WAIT parameter, see “Chapter 8. Installing a resource update list” on page xx and "Chapter 10. Using the Batch Update List utility" on page xx. image-20181126113652-2

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

Topic: Chapter 8. Installing a resource update list > Installation methods

Figure 128 has been updated and Step 4 has been added to the procedure as follows: 

2. Use the S line command to select resource update lists to install. You can select up to 255 resource update lists to install simultaneously. Press Enter to initiate the installation process. The update list entries from the update lists are shown in the following panel:

image-20181126113638-1

------------------------------------------------------------------------------
INSTALL    IMS HP Sysgen Tools - Update List Entries           Row 1 to 3 of 3
                                                                 More ->      
Target  ===> IFVX      (IMSID or Group Name)      Wait ==>                    
                                                                              
   Primary Commands:                                                          
      GO   Install these Resource Update Entries                              
                                                                              
Function  Resource    Name    List Name  List TGT        Updated           ID  
ADD       APPLCTN   DFSSAM0A  DFSSAM0A   IMS8      2017/05/06 20:47:44  P390M
ADD       DATABASE  DI21PART  DI21PART   IMS8      2017/05/06 20:48:06  P390M
UPDATE    TRANSACT  PART      DI21PART   IMS8      2017/05/06 20:48:06  P390M
*************************** Bottom of data ****************************
------------------------------------------------------------------------------
image-20181126113652-2

Figure 128. Update list entries panel (Figure 4 in KC)

3. Validate that the correct resource update lists are selected and specify the target name for which the entries are to be installed.

4. image-20181126113638-1If necessary, specify how long an IMS OM waits for a response of the IMS member level global online change process from all the members of the IMSplex. The wait value is in seconds (1 - 99999). If you do not specify the wait value, the default value of 300 seconds is used. If the resource update list includes entries that require reloading of many ACBLIB members by use of IMS member level global online change, the wait interval might expire. In this case, the IMS OM returns an error response to IMS HP Sysgen Tools, and the installation process fails. image-20181126113652-2

5. Enter the GO primary command to initiate the installation process. If the installation process identifies any conflicts that would prevent the update list entries from being successfully installed, messages are displayed that describe these conditions. Example errors are shown in the following panel:

...

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

Topic: Using the Batch Update List utility > Control cards used for Batch Update List processing

The WAIT parameter description has been added to the following paragraph: 

Control cards are used by the Batch Update List utility to specify the functions that you want. Because the only functions the Batch Update List utility can perform are Verify and Install, there are two control cards that can be used with this utility. The following general syntax rules apply to the control cards that are supplied by using the SYSIN DD statement.


  • An asterisk (*) in column 1 indicates that this is a comment statement. It is ignored by the utility. A comment card cannot be continued; you must code any following comment statements with an asterisk in column 1.
  • The first word on a statement must be either VERIFY or INSTALL, depending on the function that you want to perform.
  • Two keywords are required for each VERIFY or INSTALL statement, IMSID= and either IMSID= or TARGET=.
  • You must specify the target IMS system for the VERIFY or INSTALL function. You can specify a single IMSID using the IMSID= or TARGET= keywords, or a group of IMS systems by using the TARGET= keyword. Whatever IMSID or group name you specify must be defined to IMS HP Sysgen Tools through the IMSID or GROUP SETUP panels.
  • The NAME= keyword identifies one or more resource update list member names that are to be verified or installed. If more than one name is specified, separate the member names with a comma, and enclose the list in parentheses. For example, NAME=(MEMBER1,MEMBER2) will select resource update lists that are named MEMBER1 and MEMBER2.
  • image-20181126113638-1You can specify, by using the WAIT= keyword for the INSTALL statement, how long an IMS OM waits for a response of IMS member level global online change process from all the members of the IMSplex. The wait value is in seconds (1 - 99999). If you do not specify the WAIT= keyword, the default value of 300 seconds is used. If the resource update list includes entries that require reloading of many ACBLIB members by use of IMS member level global online change, the wait interval might expire. In this case, the IMS OM returns an error response to IMS HP Sysgen Tools, and the installation process fails. image-20181126113652-2
  • Continuation of a statement is permitted. A comma at the end of a card indicates that the statement is continued on the next line.

The following figure shows some examples of valid control cards:

image-20181126113638-1

INSTALL NAME=MEMBER1,IMSID=IMSA
      VERIFY  IMSID=IMSA NAME=( MEMBER1 , MEMBER2 )
INSTALL TARGET=GROUP2,NAME=MEMBER1,WAIT=600
 VERIFY TARGET=GROUP1,
        NAME=(MEMBER1,
              MEMBER2)
image-20181126113652-2 

Figure 135. Sample batch update list control cards (Figure 1 in KC)

You can include multiple control cards in a single issuance of the Batch Update List utility. Each statement is processed individually. When multiple members are specified on a single control card, the members are merged and processed simultaneously. When multiple members are specified on separate control cards, they are processed individually.

 
To install several resource update lists in a single batch job, it is more efficient to install all the resource update lists at once (by specifying them all in a single statement). However, if one entry fails, none of the entries in any of the update lists will be installed.

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

Topic: Troubleshooting > Runtime messages (IOH)

Messages IOH7121E and IOH7122E have been added. 

image-20181126113638-1
IOH7121E WAIT PARAMETER NOT ALLOWED FOR VERIFY STATEMENT
Explanation: The WAIT parameter was specified for a VERIFY statement. The WAIT parameter can be specified only for an INSTALL statement.
System action: The statement is ignored.
User response: Remove the WAIT parameter from the VERIFY statement.
Severity: N/A


IOH7122E WAIT VALUE EXCEEDS 5 CHARACTERS
Explanation: The WAIT value that was specified is not valid. The WAIT value must be a number between 1 - 99999.
System action: The statement is ignored.
User response: Correct the specification of the WAIT= value.
Severity: N/A
image-20181126113652-2

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

Topic: Troubleshooting > ISPF messages (IOH[A-F])


Message IOHA250 has been added. 

image-20181126113638-1
IOHA250 Invalid Wait Value
Explanation: The wait value is not valid. The value must be 1 - 99999.
System action: None.
User response: Specify a number between 1 and 99999 for the WAIT field.
image-20181126113652-2


Update 1

Date of change: January, 2019

Change description: Documentation changes for the installation store/forward function

Topics: Changes apply to multiple topics.

This topic has been updated as follows:

If an IMS system is not active at the time the resource update list is being installed,
installation fails. However, if you use the installation store/forward function, the
resource update list is automatically installed later when the IMS become active.

To install the resource update list through the ISPF user interface or as a batch job,
the target IMS must be online; otherwise, installation fails. The installation
store/forward function enables you to store the failed installation information in
the store/forward VSAM data set, categorized by IMSIDs, and to retry the installation
later when the IMS becomes active.

image-20181126113638-1Installation store/forward is available only if the store/forward VSAM data set is
specified in the batch job (IOHBLIST) or the IOHXEXEC EXEC statement.
Installation store/forward supports only INSTALL commands for resource update
lists.image-20181126113652-2

...

This topic has been updated as follows:

The process of the installation store/forward function can be divided into two
steps: storing the failed installation information and reinstalling it by running the
REDO job.

Step 1: Storing the installation information in the store/forward
VSAM data set

If any of the following situations occurred during installation of the resource
update list, the installation information for the failed IMS is stored in the
store/forward VSAM data set:

  • image-20181126113638-1The target IMS specified by the IMSID= parameter was configured as a local
    online change system or as a dynamic resource definition (DRD) system, and
    installation of the resource update list failed because that IMS system was not
    active during installation.
    image-20181126113652-2
  • None of the IMS systems in the group specified by the TARGET= parameter was 
    configured as a global online change system, and installation of the resource 
    update list failed for some of those IMS systems because they were not active.
  • image-20181126113638-1In the group specified by the TARGET= parameter, some IMS systems were 
    configured as global online change systems and others were configured as local 
    online change systems or DRD systems. Installation of the resource update list
    was successful for all the IMS systems that were configured as global online
    change, but failed for the IMS systems that were configured as local online
    change and were not active.
    image-20181126113652-2

If you specified the IMSID= parameter to install the resource update list, one
record is written in the store/forward VSAM data set. If you specified the
TARGET= parameter to install the resource update list, records are categorized by
the IMSIDs and written in the store/forward VSAM data set.

...

This topic has been updated as follows:

Scheduling the REDO job

The REDO job must be scheduled immediately after IMS is started and before the
system is opened up for processing.

Before you begin

The REDO job basically runs on the same IMS system that processes the
installation of the resource update list. To customize which target IMS systems are
processed by the REDO job, specify target IMS systems in the SYSIN control
statement.

Procedure

image-20181126113638-1You can use one of the following methods to schedule a REDO job:

  • Incorporating the REDO job scheduling into your automated operation
    procedure

    If you already have your own automated operation procedure, add REDO job
    scheduling after IMS™ is started and before the system is opened up for
    processing. Then, schedule an IMS command that activates IMS resources, such
    as /STA DC or /STA REGION, after the REDO job completion.

    You can recognize REDO job completion by an HP Sysgen Tools WTO message.
    One of the following messages is displayed, depending on the REDO job
    completion status.

    IOH7602I STORE/FORWARD PROCESSING COMPLETED DATE-TIME=yyyy.ddd-hh:mm:ss  or IOH7610W STORE/FORWARD PROCESSING COMPLETED DATE-TIME=yyy.ddd-hh: mm:ss IOHBLIST HIGHEST RC=rc

  • Using IMS TCO (time-controlled operations) to start the REDO job immediately
    at IMS startup
    image-20181126113652-2

    In order to use IMS TCO for a REDO job, register the REDO job with the
    IMS.JOBS data set that is used for the IMS /START REG command.

    When writing a TCO script, note the following:
    • Code the /START REG command for starting the REDO job at the top of the
      TCO script.
    • Set an interval time between the REDO job startup and the subsequent TCO
      script startup. Specify an appropriate interval time for your system.
    • In the subsequent script, include a command that activates IMS resources
      such as /STA DC or /STA REGION.


    In the following example, the REDO job is registered with the IMS.JOBS data set
    as "IOHREDO". The example assumes that the /STA REG command for starting
    the REDO job was added to an existing TCO script. The next command will be
    invoked three minutes after the REDO job is started.

    sample code

    For more information, see the topic "IMS time-controlled operations" in IMS
    Operations and Automation
    .

    Important: In an IMS DBCTL environment, you must implement this function
    without using TCO because of an IMS restriction. For more information, see
    "Restrictions for using the installation store/forward function" on page 56.

What to do next

If the REDO job ends abnormally for some reason, fix the error and rerun the
REDO job manually.

This topic has been updated as follows:

REDO job JCL requirements

image-20181126113638-1Sample JCL for the REDO job can be found in the IOHREDO member of the
AIOHSAMP data set.image-20181126113652-2

The following DD statements are required for the REDO job JCL:

image-20181126113638-1STEPLIB

This DD statement must refer to the IMS HP Sysgen Tools load library, SIOHLINK.image-20181126113652-2

REDOCTL

Specifies the IMSIDs of the target IMS systems on which to reinstall
resource update lists. Specify the IMSID= control statement in the
following format:

IMSID=imsid1,imsid2,imsid3,...

The IMSID= statement can be placed anywhere between column 1 and 71.
If column 1 is an asterisk (*), that line is treated as a comment line.
Use commas to separate two or more IMSIDs on the same IMSID=
statement. An IMSID= statement must be on the same line.
You can specify as many IMSID= control statements as you want, provided
that the total number of IMSIDs defined does not exceed 256.

REDORPT

Specifies the location for output reports from the installation store/forward
function. The location can be a SYSOUT file or a data set.

IOHSTFWD

Specifies the store/forward VSAM data set in which the information about
reinstalling the resource update list is stored.
The records must be fixed length. The CI (control intervals) size is 2560
bytes. The record format is illustrated in Table 7 on page 52.

image-20181126113638-1SYSUDUMP

This DD statement is used to record diagnostic information when a failure occurs in the REDO job and the Batch Update List utility.

The following DD statements are also required for the REDO job JCL because the REDO job uses the Batch Update List utility internally. For an explanation of each DD statement, see "JCL requirements" on page 180.

  • IOHOPT
  • IOHPDS
  • IOHPRINT
  • SYSIN
image-20181126113652-2

Topic: Troubleshooting > Gathering diagnostic information

This topic has been updated as follows:

Gathering diagnostic information

...

Provide additional information based on the type of problem that you experienced:

For online abends, provide the following information:

  • A screen capture of the panel that you were using when the abend
  • occurred
  • The job log from the TSO session that encountered the abend
  • The job log from the server
  • A description of the task that you were doing before the abend occurred

For errors in batch processing, provide the following information:

  • The complete job log
  • Print output
  • Contents of the data sets that were used during the processing

image-20181126113638-1For errors related to the installation store/forward data set, provide the following information: 

  • Print out of the installation store/forward data set (The second step of IOHSTF member of the SIOHSAMP data set can be used for printing.)image-20181126113652-2


Publication Number

SC27-9501-00

Copyright Date

2001, 2018

Original Publication Date

2018-12-14


Cross reference information
Product Component Platform Version Edition
IMS Tools IMS Transaction Manager Solution Pack z/OS 1.1.0

Document information

More support for: IMS Tools

Component: IMS High Performance System Generation Tools

Software version: 2.4.0

Operating system(s): z/OS

Software edition: SC27-9501-00

Reference #: 0741739

Modified date: 11 June 2019