IBM Support

IBM Security Guardium datasets on z/OS : Using alternate RECON data sets for SMF and SLDS processing

Question & Answer


Question

Can I utilize the copies of the IMS RECON data sets when processing SMF (AUIFstc) and IMS SLDS (AUILstc) data instead of the live RECON data sets.

Cause

In some instances, customers may wish to utilize copies of the IMS RECON data sets when processing SMF (AUIFstc) and IMS SLDS (AUILstc) data instead of the live RECON data sets.

Answer

This can be accomplished by adding a “//AUIARCN” DD statement to the AUIFstc and AUILstc JCLs which contain the name of the IMS system (as defined in the Guardium Appliance IMS Definition panel) along with the alternate RECON data set names that should be used when processing these two types of data sources. Specifying these alternate RECON names have no effect on any processing other than the AUIFstc and/or AUILstc tasks.

It is up to the customer to create these cataloged, VSAM copies of their live RECON data sets using IDCAMS or some other VSAM compatible method.

The data set specified by the AUIARCN DD must defined as Fixed Block (FB), Record length of 80 bytes (LRECL=80) and may be a sequential file, PDS or PDS/E.

· An asterix (*) in column 1 indicates the line is a comment.

· Keywords must start in column 1.

· No spaces are allowed within keywords and parameters.

· Multiple IMSNAME= keywords may be specified in one AUIARCN file.

· At least one RECON data set must be included under each IMSNAME identifier.

· Alternate RECON data sets must be cataloged and in VSAM format.

IMSNAME= Specifies the IMS that the following RECON1/2/3 keywords pertain to.


RECON1= Specifies the alternate data set name to be used for RECON1.
RECON1= Specifies the alternate data set name to be used for RECON2.
RECON1= Specifies the alternate data set name to be used for RECON3.


EXAMPLE:
IMSNAME=IMSV14
RECON1=IMSEA1.ALT.RECON1
RECON2=IMSEA1.ALT.RECON2
RECON3=IMSEA1.ALT.RECON3
*
IMSNAME=IMSV13
RECON1=IMSDA1.ALT.RECON1
RECON2=IMSDA1.ALT.RECON2


NEW MESSAGES:

AUIJ510I - ALTERNATE RECON DATA SETS FOUND FOR IMSNAME imsname
- RECON1: alt_dsn_1
- RECON2: alt_dsn_2
- RECON3: alt_dsn_3

Explanation: The AUIARCN DD was found in the JCL and the imsname used to when installing the active IMS policy was found in the AUIARCN file, along with alternate RECON data sets names (alt_dsn_1/2/3).
System Action: Processing continues.
User Response: None.


AUIJ511E - ALTERNATE RECON DATA SET NOT CATALOGED
- DSN: alt_dsn

Explanation: When attempting to validate the alt_dsn value, the data set was not found in the catalog.
System Action: Processing continues to validate other data set names specified.
User Response: Correct the data set name or catalog the data set.


AUIJ512E - ALTERNATE RECON DATA SET NOT A VSAM FILE
- DSN: alt_dsn

Explanation: When attempting to validate the alt_dsn value, the data set was found to not be in VSAM format.
System Action: Processing continues to validate other data set names specified.
User Response: Correct the data set name or catalog the data set.

AUIJ513E - NO VALID ALTERNATE RECON DATA SETS FOUND for IMS imsname


- - PROCESSING TERMINATED

Explanation: After data set validation completed, it was determined that for IMSNAME imsname, no valid alternate RECON data set names were specified or found..
System Action: Processing terminates.
User Response: Add or correct valid RECON data set names.

[{"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Guardium S-TAP for Data Sets on z\/OS","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"10.0;10.0.1;10.1;10.1.2;10.1.3","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}},{"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":" ","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
16 June 2018

UID

swg22013917