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 PORDER value and syntax. 2ExplanationThe statistical information address (@@FLMSTP) was 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 FLMLPGEN parser). 3ExplanationThe list information address (@@FLMLIS) was 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 FLMLPGEN parser). 4ExplanationDependency name longer than 8 characters was recognized. The dependency is not added to the dependency list. Processing continues. User responseVerify and correct the length of the dependency name. Project manager responseNone. 5ExplanationMaximum list size (LISTSIZE) was not found in parameter list. User responseNone. Project manager responseCheck the language definition syntax (LISTSIZE parameter on the OPTIONS parameter on the FLMTRNSL FLMLPGEN parser). 6ExplanationSOURCEDD parameter is greater than eight characters. User responseContact the project manager. Project manager responseCheck the language definition syntax (SOURCEDD parameter on the OPTIONS parameter on the FLMTRNSL, FLMLPGEN parser). 7ExplanationThe number of parsed dependencies exceeds the size of the $list_info array, that 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. 9ExplanationBad value encountered for LISTINFO, LISTSIZE or STATINFO. User responseContact the project manager. Project manager responseCheck the language definition syntax (OPTIONS parameter on the FLMTRNSL, FLMLPGEN parser). 10ExplanationMember name not found. User responseNone. Project manager responseCheck the language definition syntax. 12ExplanationInvalid language. User responseContact the project manager. Project manager responseCheck the language definition syntax (LANG parameter on the OPTIONS parameter on the FLMTRNSL, FLMLPGEN parser). 22ExplanationI/O error. User responseCheck the source code for a dependency name greater than 8 characters. The I/O error may occur when the TSO prefix is not set and the parser attempts to allocate an error data set. If the TSO prefix was not set then set the TSO prefix and run the parse again if you cannot locate the dependency name that is greater than 8 characters. Project manager responseVerify the data sets used by the parser OPEN and CLOSE properly. 101 - 199ExplanationThe data set specified by the PARSEDSN keyword could not be allocated. User responseContact the project manager. Project manager responseVerify that the data set designated by the keyword exists. 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 to see 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 any necessary corrections to the project definition; assemble and link the project definition. 
|
 Copyright IBM Corporation 1990, 2014 |
