z/OS ISPF Software Configuration and Library Manager Guide and Reference
z/OS ISPF Software Configuration and Library Manager Guide and Reference
Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
0 z/OS ISPF Software Configuration and Library Manager Guide and Reference SC19-3625-00 |
|
ExplanationIndicates successful completion. User responseNone. Project manager responseNone. 1ExplanationData set name not found in parameter list. User responseContact the project manager. Project manager responseCheck the language definition syntax (PARSEDSN parameter on the OPTIONS parameter on the FLMTRNSL FORTRAN parser). Verify that PORDER=1 or PORDER=3 was used on the FLMTRNSL macro of the language definition. A PORDER of 0 or 2 in the FLMTRNSL macro for the FLMLPFRT parser will result in FLMLPFRT receiving control without the OPTION list. PORDER 0 and 2 are used for situations in which there are no OPTION lists. 2ExplanationThe statistical information address (@@FLMSTP) is not found in the parameter list. User responseContact the project manager. Project manager responseCheck the language definition syntax (STATINFO parameter on the OPTIONS parameter on the FLMTRNSL FORTRAN parser). 3ExplanationThe list information address (@@FLMLIS) is not found in the parameter list. User responseContact the project manager. Project manager responseCheck the language definition syntax (LISTINFO parameter on the OPTIONS parameter on the FLMTRNSL FORTRAN parser). 4ExplanationA dependency name was encountered that had more than 8 characters. The name is ignored and processing continues. User responseCheck the source member for dependency names longer than 8 characters. Dependency names are restricted to a length of 1 to 8 characters. Project manager responseThe language definition can be changed for GOODRC=4 if it is acceptable to ignore the dependency names that are longer than 8 characters. 5ExplanationThe STATINFO, LISTINFO, and/or LISTSIZE keyword parameters are invalid. User responseCheck the language definition for the correct values for keyword parameters STATINFO, LISTINFO, and LISTSIZE. Project manager responseThe invalid keyword parameters for FLMLPFRT OPTIONS in the language definition should be corrected and the project definition assembled and linked. 8ExplanationThe number of parsed dependencies exceeds the size of the $list_info array, which is specified by the BUFSIZE parameter on the FLMLANGL macro. User responseEither reduce the number of parsed dependencies for the member or contact the project manager. Project manager responseIncrease 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. 10ExplanationThe member name specified by the parse parameter is blank. User responseNone. Project manager responseCheck the language definition syntax and member specification. 12ExplanationThe LISTSIZE keyword parameter in the OPTIONS is too small. There is not enough room for one element in the dependency array. User responseContact the project manager. Project manager responseUpdate the project definition, assemble, and link-edit. LISTSIZE must be set to @@FLMSIZ in order to get a proper value for BUFSIZE. 24ExplanationParser was not linked AMODE(24), RMODE(24). User responseContact the project manager. Project manager responseReinstall the parser by relinking it AMODE(24). See ISPF log for more details. 100ExplanationThe value for the PARSEDSN keyword is invalid. User responseCheck the language definition and verify that PARSEDSN keyword value is valid. Project manager responseNone. 101 - 199ExplanationThe data set specified by the PARSEDSN keyword could not be allocated. User responseVerify that the data set designated by the keyword exists. Project manager responseNone. 201 - 299ExplanationThe data set specified by the PARSEDSN keyword could not be opened, or is already opened. User responseVerify that the data set exists, is not in use, and has not been allocated with a disposition of SHR or MOD. Project manager responseNone. 401 - 499ExplanationAn error occurred reading the data set specified by the PARSEDSN keyword. The data set is either empty, not opened for input, or has exceeded its space capacity. User responseVerify that the data set exists, it is not empty, and the space allocation will support the process. Project manager responseNone. 500ExplanationAn error occurred when closing the file or when freeing storage. User responseContact the project manager. Project manager responseContact your IBM® Service Representative. 599ExplanationAn ABEND was detected during I/O or allocation of the data set to be parsed. User responseCheck if the data set member to be parsed exists. An improper value for STATINFO in the OPTIONS of the FLMTRNSL for the parser can be another cause. Project manager responseMake sure the data set member exists. Make corrections to the project definition; assemble and link the project definition. 
|
 Copyright IBM Corporation 1990, 2014 |
