Return Codes from SMFDLS and its IFASMFDL exits

SMFDLS Control Statement Reference › Return Codes from Logstream Dumping › Return Codes from SMFDLS and its IFASMFDL exits

Return Codes from SMFDLS and its IFASMFDL exits

Non-zero return codes from SMFDLS are numbered from 100 to 999.
Any return code that is less than 100 comes from IFASMFDL, with the exception of return code 4, which can come either from IFASMFDL or from CA SMF Director.
Return codes of 505 through 599 originate in CA SMF Director itself.
Return codes under 1000 are from SMFDLS itself, from IFASMFDL, or from the CA SMF Director dump process.
Return codes from 1000-1999 are from the IFASMFDL Exit 1 program, and 2000-2999 are from the IFASMFDL Exit 2 program.
The IFASMFDL Exit 3 program does not issue any return codes or abends.

Return Code	Explanation and Action
100	Region error. Increase the REGION on the EXEC statement in the JCL and retry the dump.
110	SMFDLSPR did not open. Make sure it is allocated and set up as a print file and retry the dump.
111	SMFDLSIN did not open. Make sure it is allocated and set up as an input file with LRECL=80 and retry the dump.
120	Syntax error in SMFDLSIN control statements. Messages indicating which statements contain errors will appear in the SMFDLSPR printed report. Correct any errors and retry the dump.
121	Invalid logstream name. Logstream names can be up to 26 characters, consisting of three nodes of 8 alphanumeric or national characters. The nodes themselves must begin with an alphabetic character or national character. Additionally for SMF recording, the logstream name must begin with the string IFASMF. Correct any errors and retry the dump.
122	No LSNAME control statement found and the JCL control statement was also not found in the control statements. Place either of these control statements into the input stream and retry the dump.
123	No UNIT or STORCLAS control statement found. Make sure one or the other is included in the input stream and retry the dump.
124	Either STARTTIME was found in the control statements without a STARTDATE, or ENDTIME was found in the control statements without an ENDDATE. Correct any errors and retry the dump.
140	Failure to obtain the necessary ENQs for dumping. Contact your systems programmer.
141	Name/token services failure. Contact your systems programmer.
150	SCDS not allocated. Ensure the SCDS data set is allocated to the ddname SCDS. Correct any errors and retry the dump.
160	SCDS failed to open. Ensure the SCDS data set is allocated to the ddname SCDS. If it is, consult the error messages and error code in the resulting IBM messages. Correct any errors and retry the dump.
161	Region error for SCDS record buffer. Increase the REGION parameter in the JCL and retry the dump.
162	An unexpected error occurred when reading the SCDS data set. Contact CA Technical Support. Be prepared to provide a copy of your SCDS data set as well as any printed output.
163	SCDS not up to version level for logstream support. Perform a backup and restore of the SCDS with the latest version of CA SMF Director with all maintenance applied and retry the dump.
164	Configuration not found. There is no configuration in the SCDS for the system that produced the SMF records to be dumped. Define the system to the SCDS using the COMPILE CONFIGURATION control statement, making sure to include the logstream names needed in the DUMPOPTIONS. After the compilation, retry the dump.
165	Configuration has no logstreams. There is a configuration in the SCDS for the system that produced the SMF records, but there are no logstreams defined to the configuration. Recompile the configuration and ensure that the needed logstreams are named in the DUMPOPTIONS. After the compilation is complete, retry the dump.
166	Logstream not found. The configuration in the SCDS for the system that produced the SMF records has logstreams defined, but not the logstream named in the LSNAME control statement. After verifying that the logstream name in the LSNAME control statement is correct, recompile the configuration adding the logstream name. After successful compilation, retry the dump.
167	Region error for SCDS record buffer. Increase the REGION parameter in the JCL and retry the dump.
170	Dynamic allocation failure for the SYSIN data set that will be used as input to IFASMFDL. Check and make sure that the SYSIN DD is not present in your JCL. If it is not present, ensure that the value of the UNIT or STORCLAS contains a valid value for your data center. If all of these check out, contact CA Technical Support and be prepared to provide the return codes and messages produced in the SMFDLSPR printed output. Otherwise correct any errors and retry the dump.
171	SYSIN failed to open for output. After allocating the SYSIN data set, SMFDLS could not open it for output. See the error messages produced by IBM that come with the OPEN failure. Correct any errors and retry the dump.
172	CLOSE failed for SYSIN. The constructed control statements for IFASMFDL were written to the SYSIN file, but the file did not close. See the error messages produced by IBM that come with the CLOSE failure. Correct any errors and retry the dump.
180	Attach failed for CA SMF Director. The main CA SMF Director load module could not be attached by SMFDLS so that the SMF records can be processed. See any IBM error messages, correct any errors found, and retry the dump.
181	IFASMFDL encountered an error in processing and SMFDLS needed to post termination for CA SMF Director as opposed to IFASMFDL User Exit 3. Likely causes for this condition are as follows: A logstream has been defined in a system configuration in the SCDS but does not exist in the SMF configuration for that system. One or more of the CA SMF Director logstream dump process exits are not registered with SMF. Examine the messages that have been produced by IFASMFDL and take appropriate action based on the information in the messages and the message descriptions in the IBM MVS System Messages documentation.
400	LOAD failed for IFASMFDL. Ensure that the dump job is being run on a system that is z/OS 1.9 or higher. If the system is z/OS 1.9 or higher, consult with your systems programmer.
401	No logstreams were generated in the SYSIN control statements. Contact CA Technical Support. Be prepared to provide your output as well as a copy of your SCDS data set.
500	CA SMF Director abended during the run. The attached subtask will have diagnostics available and error messages. See the Message Guide and the Systems Programmer Guide, correct any errors found, and retry the dump.
505 up to 599	CA SMF Director encountered an error during processing and completed with a non-zero return code. See the output in the CAIPRINT output file as well as the Message Guide. Correct any errors and retry the dump.
1001*	Insufficient region for exit processing. Increase the region size and retry the dump.
1002*	Name/token services failure. Contact your systems programmer.
1003*	Corrupt token found. Contact CA Technical Support. Have ready the printed output from your dump job.
1004	Mismatched logstream name. The logstream name indicated in IFASMFDL is not the same as the logstream name indicated in the parameters provided to SMFDLS.
1005*	CA SMF Director early termination. The attached subtask of CA SMF Director terminated. Look at the messages in the CAIPRINT Audit Trail Report and correct any errors; then retry the dump.
2001*	CA SMF Director early termination. The attached subtask of CA SMF Director terminated. Look at the messages in the CAIPRINT Audit Trail Report and correct any errors; then retry the dump.

* Return codes marked with an asterisk are issued as user abends and not as actual return codes from SMFDLS.

Tell Technical Publications how we can improve this information