|
Code |
Explanation |
|---|---|
|
1500 |
Unable to open MAINTIN |
|
1501 |
Unable to open MAINTOUT |
|
1502 |
Invalid control statement verb (not CREATE) |
|
1503 |
CA Top Secret cannot be active for CREATE |
|
1504 |
Invalid control statement |
|
1505 |
Syntax error in control statement |
|
1506 |
Unable to open Security File |
|
This abend is also displayed as a normal part of running TSSMAIND. (TSSMAIND is used during installation to calculate the number of blocks required for the Security File). |
|
|
1508 |
Password required for SCA definition |
|
1509 |
Non‑numeric specified. |
|
1510 |
Error creating Security File. See SYSPRINT output for further details. |
|
1513 |
Not Master SCA |
|
1514 |
Same as 1506 for DUMP option |
|
1515 |
Security File BLOCKSIZE is different from JCL‑supplied BLOCKSIZE. Do not code the BLKSIZE keyword in the JCL. |
|
1516 |
Unable to open Audit/Tracking File. |
|
1517 |
Unable to open Recovery File or the Recovery File was specified incorrectly with Keys. |
|
1518 |
Blocksize too small |
|
1519 |
Unable to open CPF Recovery File |
|
1520 |
VSAMFILE initialization failed. Note: TSSMAINS can be run only once using the same VSAMFILE DD data set. To rerun TSSMAINS, delete and recreate the VSAMFILE data set. |
|
1521 |
AESENCRYPT can only be specified when running CA Top Secret r14 or higher |
|
Review the sysprint output of the TSSMAINT job for further information about the error or abend. |
|
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|