Informational only.
Informational only.
Informational only.
Informational only.
The LOAD command specifies data set <pdsname>, which is not a partitioned data set.
The LOAD command specifies a data set that cannot be successfully opened. Determine why the OPEN failed, correct the problem, and then issue the command again.
The read has failed to list the specified directory. Contact CA Technical Support.
The LOAD command specifies a data set of *, but no data set has been previously specified. Issue the LOAD command again, specifying a particular data set.
The data set <dsname> is not a load library.
The data set specified on the LOAD command is empty.
The member <memname> is not in data set <dsname>. Verify the location of the member and then issue the command again.
The LOAD command has used the alias <alias-used> to specify a member name. Aliases are not allowed with the LOAD command. The message shows the real member name <real-name>. Issue the command again, specifying the real member name.
The LOAD command has specified the alias <name>, but it cannot be determined what it is an alias of. Aliases are not allowed with the LOAD command. If the real name for the alias had been determined, message LPA$016E would have been displayed. Use the LISTDIR command to determine the real name for the alias you used. Issue the command again, specifying the real name.
The module <modname> specified with the LOAD command has not been created by the linkage editor, so it cannot be loaded.
The LOAD command will not load the nonexecutable module <modname>.
The LOAD command will not load the nonreentrant module <modname>.
The LOAD command will not load module <modname>, which has unsupported options. Currently unsupported options include OVERLAY, SCATTER, and TEST.
The module <name> has too many aliases to load. The LOAD command loads a main member name and up to 16 aliases. If you must load the member, delete enough aliases to bring the number of aliases to 16 or less. After you have deleted the aliases, issue the LOAD command again.
The request for global module storage has failed. Determine why the request failed, correct the problem, and then issue the command again.
The LOAD for module <modname> has abended. <code> is the abend code. Determine why the abend occurred, correct the problem, and then issue the command again.
The request for global storage has failed, and with it, the LOAD command. Determine why the request failed, correct the problem, and then issue the command again.
The module <modname> has been loaded successfully to common area storage. A CDE describing it has been added to the active LPA queue.
The module <modname> specified with the DELETE command cannot be found on the active LPA queue.
The data set name <dsname> specified with the LOAD command is not authorized by APF. Authorize the data set and issue the command again.
The CDS instruction to remove a CDE from the active link pack area queue has failed. This occurs only when some other process updates the same field at the same instant. Issue the DELETE subcommand again.
The DELETE command has successfully deleted the module <modname> from the active LPA queue. The storage the module occupied is not freed, however, because the FREE option was not specified with the DELETE command.
The DELETE command has successfully deleted module <modname> from the active LPA queue. It has also freed the storage the module occupied.
The DELETE command has been issued with the FREE option for module <modname> on the active LPA queue, but the module was not loaded using this product. Only modules loaded by this product can be deleted.
The OPEN for the LOAD command has abended. <code> is the abend code. Determine why the OPEN abended, correct the problem, and then issue the command again.
Informational only.
Informational only.
Informational only.
Informational only.
Informational only.
|
Copyright © 2013 CA.
All rights reserved.
|
|