search cancel

Implementing ACF2/IMS into a new IMS Subsystem

book

Article ID: 256348

calendar_today

Updated On:

Products

ACF2 - z/OS ACF2 - MISC

Issue/Introduction

Implementing ACF2/IMS into a new IMS Subsystem.

Have cloned an IMS system, and started a new one.  Whilst this starts, the /ACF SHOW STATE command shows it is using options/default userids/classes, etc... from that system that was copied.

 

Environment

Release : 16.0

Resolution

In the IMS Records Design Concepts and Features, the 'IMS Record Key' describes how the ACF2/IMS interface determines what ACF2/IMS control records to use.

The ACF2/IMS EXITS, NETWORK, OPTS, RESOURCE, SIGNON, STORAGE, SYSPLEX and WTO records are designed to provide a large assortment of security controls and features to let security administrators select the type of security most appropriate for your site's needs. 

Each ACF2/IMS record uses the DIVISION(musid|jobname) as part of the record key in the ACF2 VSAM INFOSTG database. The DIVISION is a one- to eight-character value defining the specific control region that uses this record. If you want to have more than one control region use this record, you can use the MDIVISION field instead of the DIVISION field and the standard ACF2 masking character, the asterisk (*).

If you do not want to use masking, the DIVISION value must match the MUSID field value in the control region's logonid record. If you do not specify the MUSID field value, the DIVISION value must match the job name or the procname specified in the JOB statement in the region's startup JCL. Most security administrators prefer to use the MUSID field value because it is not affected by changes that are made to the startup JCL. If you use the job name or procname as the DIVISION value, any changes made to the JCL might require you to change the DIVISION value so that it matches the JCL.

Based on this issue description it appears that either on the new system the IMS Control region logonid specifies the MUSID of the copied system or the IMS Control region procname specified in the JOB statement specifies the DIVISION of the copied system. 

To address the issue of picking up the options/default userids/classes, etc... from that copied system you can do one of the following.

  1. Define new ACF2/IMS records on the new system with a new Division for the new system and specify that DIVISION in the MUSID of the IMS Control region's logonid on the new system.
  2. Define new ACF2/IMS records on the new system with a new Division for the new system and change the job name or the procname specified in the JOB statement in the region's startup JCL to match that MUSID.
  3. Change the copied ACF2/IMS records(in the INFOSTG database) on the new system from the copied system's values to the required values for the new system.