This section details messages generated in the course of processing, specifically regarding the CONSCAN Utility. Possible causes and corrective actions to take in error situations are described. All CONSCAN utility messages are routed to SYSPRINT and the z/OS console.
Reason:
An attempt was made to initialize a CONSCAN control block, which is already defined.
Action:
Contact your administrator.
Reason:
An attempt was made to add a CONSCAN control block, which is already defined.
Action:
Contact your administrator.
Reason:
An attempt was made to read a CONSCAN control block, which was not found.
Action:
Contact CA Technical Support.
Reason:
An attempt was made to delete a CONSCAN control block; which was not found.
Action:
Contact your administrator.
Reason:
An attempt was made to free a CONSCAN control block, which was already defined.
Action:
Contact your administrator.
Reason:
An attempt was made to insert an item in a CONSCAN control block, which was not found.
Action:
Contact your administrator.
Reason:
During scanning, an error was detected in the PARMSCAN rules.
Action:
Review the output, correct the error, and rerun the scan.
Reason:
A syntax error was detected in one of the COMMENT control cards.
Action:
Correct the syntax error and rerun the job.
Reason:
A syntax error was detected in one of the SCANTYPE control cards.
Action:
Correct the syntax error and rerun the job.
Reason:
A scanner subroutine returned a non-zero value.
Action:
Review the output files for the cause. If a secondary error message is not present, contact your administrator.
RC=4 - NO RECORD FOUND IN SCANNER
Reason:
The target Element to scan is empty.
Action:
Either correct the target Element so that it contains data, or choose another Element and rerun the scan.
Reason:
A COMMENT syntax error was detected in the PARMSCAN rules member.
Action:
Correct the rules syntax and rerun the scan.
Reason:
A RULES syntax error was detected in the PARMSCAN rules member.
Action:
Correct the rules syntax and rerun the scan.
Reason:
The DD for SYSPRINT was missing from the supplied JCL.
Action:
Correct the JCL and rerun the job.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|