Naming a CA View Report Based on Sysout Class
search cancel

Naming a CA View Report Based on Sysout Class

book

Article ID: 4939

calendar_today

Updated On:

Products

Deliver View

Issue/Introduction

In converting from another report repository product to CA View, the client wants to append the report's sysout class to the Sysout ID, for proper identification.

 

Environment

CA View - All releases

Resolution

In their SARSTCUX exit, the client has code such that the sysout class for a report is appended to the Jobname (for instance, JOBNAME1:A), to create the Sysout ID of the report. 

In their ERO table, to be able to apply different retentions to reports from different sysout classes, the client will be using entries something like the following: 

/********:A ALL DRETPD=n RETPD=nnn 

/********:C ALL DRETPD=n RETPD=nnn 

/*******:A ALL DRETPD=n RETPD=nnn 

/*******:C ALL DRETPD=n RETPD=nnn 

/******:A ALL DRETPD=n RETPD=nnn 

/******:C ALL DRETPD=n RETPD=nnn 

/*****:A ALL DRETPD=n RETPD=nnn 

/*****:C ALL DRETPD=n RETPD=nnn 

/****:A ALL DRETPD=n RETPD=nnn 

/****:C ALL DRETPD=n RETPD=nnn 

/***:A ALL DRETPD=n RETPD=nnn 

/***:C ALL DRETPD=n RETPD=nnn 

/**:A ALL DRETPD=n RETPD=nnn 

/**:C ALL DRETPD=n RETPD=nnn 

/*:A ALL DRETPD=n RETPD=nnn 

/*:C ALL DRETPD=n RETPD=nnn 

/* ALL DRETPD=n RETPD=nnn

 

Note: The colon (:) in the Sysout ID is only one of many special characters recognized by ERO.