Previous Topic: SCRN - SCREENNext Topic: SECU - SECURITY


SECL - Security Report Utility

SECL001I Security report ended with return code=<xx>

The report utility job EXECSECL has completed with return code <xx>. The return codes are explained below:

Return Code and explanation:

SECL002E Invalid dataset attributes for <ddname> dataset

Invalid DCB parameters were detected for data set <ddname>. The completion code is set to 12 and the job terminates. Check the SYSPRINT and SYSOUT reports for error messages.

SECL003W User <userid> is defined in multiple groups

User <userid> was found to be present in multiple security groups. The completion code is set to 4. Review the User ID/Cross-Reference Report for the named user to determine which groups the user ID is defined in. If appropriate, delete the user from the groups that you want to deny the user access to.

SECL004E DDname <var1> not allocated

An attempt was made to allocate a security data set for the report, but the attempt failed. Check for other messages to see why the allocation failed.

SECL009E Internal error - <var1>, RC=<var2>

An attempt was made to sort security data, but the attempt failed. Contact CA Technical Support.

SECL010I Requested group, <grname>, not found in security dataset

Group <grname> was specified on a REPORT GRPDET parameter, but was not found in the security data set. The completion code is set to 4. Remove the group from the REPORT GRPDET parameter and run the job again.

SECL011E Unrecognized control statement <string>

An unrecognized control statement <string> was encountered while processing input parameters. Completion code is set to 8 and the job terminates. Check the SYSPRINT and SYSOUT reports for error messages. Verify the input parameters and run the job again.

SECL012E Unrecognized <parm> parameter <string>

An unrecognized control statement <string> was encountered while processing the <parm> control statements. Completion code is set to 8 and the job terminates. Check the SYSPRINT and SYSOUT reports for error messages. Verify the control statements and run the job again.

SECL013E Expected <parm> operand not found

An operand required for the <parm> control statement was not found. Completion code is set to 8 and the job terminates. Check the SYSPRINT and SYSOUT reports for error messages. Verify the control statements and run the job again.

SECL014E Unbalanced parenthesis detected processing <parm> parameter

Unbalanced parentheses were detected while processing the <parm> control statement. Completion code is set to 8 and the job terminates. Check the SYSPRINT and SYSOUT reports for error messages. Verify the control statements and run the job again.

SECL015E Required USER= operand not found

The USER= parameter must have at least one operand specified. Completion code is set to 8 and the job terminates. Check the SYSPRINT and SYSOUT reports for error messages. Verify the control statements and run the job again.

SECL016E GRPDET and USER= not allowed in the same run

GRPDET and USER parameters were coded in the same execution of EXECSECL. This is not allowed because the GRPDET parameter causes the group security records to be sorted. The sorting can cause the user group determination to function incorrectly. Completion code is set to 8 and the job terminates. Remove one of the control statement parameters and run the job again.

SECL017E LINECNT parameter value invalid

The LINECNT parameter must be a two-digit numeric value between 20 and 99. Completion code is set to 8 and the job terminates. Correct the LINECNT parameter and run the job again.

SECL018E Userid/Group name length error

This error can occur when processing the USER or GRPDET parameter. The specified value must be eight characters or less in length. Completion code is set to 8 and the job terminates. Correct the USER or GRPDET parameter and run the job again.

SECL019E <parm> operand is ambiguous - <string>

The <parm> control statement operand is not long enough to be unique. Completion code is set to 8 and the job terminates. Specify more characters for <string> so that the control statement operand is unique.

SECL020E Control statement has been previously encountered - <string>

The control statement <string> was already encountered while processing parameter input. Control statements may be specified only once. Completion code is set to 8 and the job terminates. Remove the duplicate control statement and run the job again.