0

z/OS ISPF Software Configuration and Library Manager Guide and Reference
SC19-3625-00

Explanation

Indicates successful completion.

User response

None.

Project manager response

None.

4

Explanation

The dependency name does not match the source code for one of the following reasons:

The dependency is greater than 8 characters. The error message in userid.SCLMERR.LISTING is:
```
4
line
dependency
```
where line is the source line that contains the dependency, and dependency is the dependency that exceeded 8 characters.
The dependency name flows into column 72.
The error message in userid.SCLMERR.LISTING is:
```
4
line
dependency
```
where line is the source line that contains the dependency, and dependency is the dependency that extends into column 72. dependency will be positioned under its occurrence in line to show that it is too far over in the source file.
The dependency name after a COPY is prefixed by an ampersand (&).
The error message in userid.SCLMERR.LISTING is:
```
4
line
&
```
where line is the source line that contains the dependency that begins with an ampersand, and & is printed under its occurrence in line.
Mismatched quotes - a single or double quote was found that did not have a matching closing quote.
The error message in userid.SCLMERR.LISTING is:
```
4
mark line_no
```
where mark is either a single or double quotation mark, and line_no is the line number that contains the unmatched quotation mark.

The dependency is not added to the list. Processing continues.

User response

Change the syntax to fit the parser.

Project manager response

None.

8

Explanation

The number of parsed dependencies exceeds the size of the $list_info array, which is specified by the BUFSIZE parameter on the FLMLANGL macro.

The error message in userid.SCLMERR.LISTING is:

8
line
dependency

where line is the source line that contains the dependency, and dependency is the dependency that exceeded the space allocated for the list.

User response

Either reduce the number of parsed dependencies for the member or contact the project manager.

Project manager response

Increase the buffer size (BUFSIZE=) on the FLMLANGL macro for the appropriate language definition. Be sure that LISTSIZE on the FLMTRNSL macro is set to @@FLMSIZ. Reassemble and relink the project definition.

10

Explanation

FLMTRNSL parameters are incorrect or are not specified.

The error message in userid.SCLMERR.LISTING is:

10
bad_parms

where bad_parms are the parameters that are incorrect or not specified.

User response

Contact the project manager.

Project manager response

Verify that the FLMTRNSL parameters for the FLMLRASM parser are valid and complete.

12

Explanation

Issued by TSOLNK; the parser was not found in the data set specified on the DSNAME parameter of the FLMTRNSL macro.

User response

Contact the project manager.

Project manager response

Verify that the value of the DSNAME parameter on the FLMTRNSL macro is correct.

16

Explanation

Error opening the error listings file.

User response

Contact the project manager.

Project manager response

Ensure that user has the authority to create and write to the file userid.SCLMERR.LISTING.

20

Explanation

Error closing the source file.

User response

Contact the project manager.

Project manager response

Contact your IBM® service representative.

22

Explanation

An I/O error occurred in the DCB while reading input. Processing stops.

User response

Contact the project manager.

Project manager response

Contact your IBM service representative. Verify that the SOURCE DDNAME is allocated correctly. Verify that the data set and member to parse exist. Verify that the FLMALLOC macro is complete and valid for the parser.

40

Explanation

SCLM was not successful in invoking FLMLRASM using IKJEFTSR (TSOLNK).

User response

Contact the project manager.

Project manager response

FLMLRASM does not return a 40. A 40 can be encountered from SCLM for CALLMETH=TSOLNK. TSOLNK is used for executing interpretive REXX. A 40 means IKJEFTSR (TSOLNK) was not successful.