SARPAR05 then U0001 in CA View using new STORGRP definition in ERO table
search cancel

SARPAR05 then U0001 in CA View using new STORGRP definition in ERO table


Article ID: 207466


Updated On:




- I added a new STORGRP definition to CA View via SARINIT and assigned it using a new ERO table entry that I added. Now the CA View backup is abending with the following messages:

SARPAR05  (Card 44) Invalid value for keyword=STORGRP, ID=JHS*, - skipping to next control card  
SARBKU30  *  CAVIEWTS Backup task abended with code U0001


- Here is the STORGRP definition I added via SARINIT:



- Here is the ERO table statement that was added:

/JHS*                             ALL DRETPD=14  RETPD=1825 STORGRP=YEAR5


I have an almost identical STORGRP definition and ERO table statement used for assigning 1 year retention periods and there are no issues using that. I can't see why CA View is having a problem with the new STORGRP definitions. Any ideas?


Release : 14.0

Component : CA View


The new statement exceeded the LENGTH restriction for an ERO table statement.

The '5' in YEAR5 was in column 73, which is one character over the limit of 72 in a PDS member that is LRECL=80.


The problem was easily resolved by removing an extra space from between the SYSOUTID (max length=32) and the 'ALL' parameter on the problem ERO table statement.

I was suggested that the customer remove this same extra space from all of their ERO table statements, so this doesn't accidentally happen again.
The rules for defining ERO table statements are as follows:

• The data set can be either a sequential file or a member of a partitioned data set. The data set attributes should be
Fixed or Fixed Blocked with a Logical Record Length from 80 to 256 characters in length. Code the slash in column 1
followed immediately by the SYSOUT ID.

• One or more blanks must follow the SYSOUT ID and separate it from the ERO table parameters.

• Parameters are separated by one or more blanks and/or commas, and can be specified in any order.

• A statement that exceeds the Logical Record Length minus 8 characters must be continued on additional statements.
The last 8 columns of each logical record are reserved for statement numbering. When continuing a statement,
interrupt the statement between complete parameters only, and omit the slash on the continuation statement.

• An asterisk in column 1 indicates a comment line.

Additional Information

These rules are documented in the Write Statements section of documentation.......