z/TPF Program Management - IBM
z/TPF Program Management - IBM
z/TPF Program Management - IBM
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
0 8<br />
0<br />
v A return code indicating the level of success of the loading phase of the offline<br />
load.<br />
The return code for the entire offline load is the greater of the two return codes.<br />
The following defines the return code values.<br />
Explanation: No errors occurred; no warnings were<br />
generated.<br />
System action: The offline load is completed.<br />
User response: Use the appropriate online loader to<br />
load the components or programs to your z/<strong>TPF</strong><br />
system:<br />
1. If you did an offline E-type load, use the ZOLDR<br />
command.<br />
2. If you did an offline general file load, ACPL will start<br />
automatically when you IPL the loader general file.<br />
3. If you did an offline image load, use the ZTPLD<br />
command.<br />
See z/<strong>TPF</strong> Operations for more information about the<br />
ZOLDR and ZTPLD commands. See “Online general file<br />
loader component (ACPL)” on page 23 for more<br />
information about the ACPL program.<br />
4<br />
Explanation: An error occurred because there was an<br />
unexpected line in the loader input file.<br />
For example, this return code is generated for the<br />
following errors:<br />
v A line started with a slash-asterisk (/*) indicating that<br />
the line is a comment. A closing asterisk-slash (*/)<br />
was not found before the end of the file. The offline<br />
loader assumes that the end of the file is the end of<br />
the comment.<br />
v The @INCLUDE control statement was started with<br />
@INCLUDE, but a file was not specified.<br />
v A processor was specified for something other than a<br />
processor-unique keypoint.<br />
v An object file was specified for a control statement<br />
other than @APPLICATION.<br />
v A control statement was misspelled; for example,<br />
@APPLICATOIN rather than @APPLICATION.<br />
v A control statement includes extra text that was not<br />
expected.<br />
System action: The offline loader program makes<br />
assumptions about the unexpected lines and completes<br />
the load.<br />
User response: Complete the following steps:<br />
1. Review the errors and determine if the assumptions<br />
made by the loader were correct.<br />
2. Do one of the following:<br />
122 z/<strong>TPF</strong> <strong>Program</strong> <strong>Management</strong><br />
8<br />
v If the assumptions made by the offline loader<br />
were correct, use the appropriate online loader to<br />
load the components to your z/<strong>TPF</strong> system:<br />
a. If you did an offline E-type load, use the<br />
ZOLDR command.<br />
b. If you did an offline general file load, ACPL<br />
will start automatically when you IPL the<br />
loader general file.<br />
c. If you did an offline image load, use the<br />
ZTPLD command.<br />
See z/<strong>TPF</strong> Operations for more information about<br />
the ZOLDR and ZTPLD commands. See “Online<br />
general file loader component (ACPL)” on page<br />
23 for more information about the ACPL program.<br />
Consider correcting the loader input file so that<br />
these errors are not repeated in the future.<br />
v If the assumptions made by the offline loader<br />
were incorrect, make the necessary corrections to<br />
the loader input file and run the offline load again.<br />
Explanation: An error occurred that impacts the<br />
output of the offline load.<br />
For example, this return code is generated for the<br />
following error:<br />
v There is an entry point name that is exported by<br />
more than one shared object.<br />
System action: If this return code is for the parsing<br />
phase of the load, the loading phase is not completed.<br />
If this return code is for the loading phase, the load is<br />
completed without the component that caused the error.<br />
User response: Do one of the following:<br />
v If the error occurred during the parsing phase,<br />
complete the following steps:<br />
1. Review the error message and correct the loader<br />
input file.<br />
2. Run the offline load again.<br />
The loading phase will not begin until the parsing<br />
phase has completed with a return code of 0 or 4.<br />
v If the error occurred during the loading phase,<br />
complete the following steps:<br />
1. Review the error message and make the<br />
necessary corrections.<br />
2. If your load requires the component that caused<br />
the error, run the offline load again.