Chapter 105 SRL (Shared Run-time Libraries) Messages

The messages in this chapter are sent on behalf of the ZTILT utility. ZTILT specifies the public shared run‑time libraries (SRLs) that are to be loaded when the processor loads. A public SRL is available to all native processes running on the processor. The C run‑time library and parts of the Open System Services (OSS) API are in public SRLs. For more information on SRLs, see the nld and noft Manual.

The subsystem ID displayed for these messages includes SRL as the subsystem name. The following example shows the format for SRL operator messages as they are sent to printers, log files, or terminals:

12:53 13OCT95 243,00,037 TANDEM.SRL.D40 108 Located SRL#1 ZCPLGSRL \DALLAS.$SYSTEM.SYS03.ZCPLGSRL OBJ GMT: 09-Oct-95 15:35:46 EOF: 421912 EXDIGEST: 725DD2ED35CBFC511C0CE78D76E6460F




	NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15.

100

SRL_TABLE_ADDRESS already loaded or corrupt.

Cause The internal public shared run‑time library (SRL) table in the processor’s memory has already been loaded or has been corrupted.

Effect ZTILT loading is terminated. Any further activity using public SRLs, such as loading them or running a client with them, causes unpredictable results.

Recovery Reload the affected processor or system. If the error persists, contact your service provider and provide all relevant information as follows:

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as trace files and a processor dump

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

101

File Error file‑error trying to find ZTILT program file filename.

`file‑error`	specifies the file‑system error that occurred.
`filename`	is the name of the ZTILT program file.

Cause A file‑system error occurred while trying to locate the ZTILT program file.

Effect ZTILT is not loaded, and all of its related public shared run‑time libraries (SRLs) are not loaded. Your applications may not be available, depending on the degree to which your application programs are dependent on public SRLs. If this error occurs during system load, this may affect applications across the system.

Recovery Examine the file‑system error and the specified ZTILT program file to determine the cause of the error, and attempt to correct the problem. For example, file‑system error 11, indicating that the file was not found, might have been encountered because ZTILT was not placed in the cold‑load SYSnn subvolume. See Appendix B, for a description of the given error. For more detailed information on file‑system errors including recovery actions, see the Guardian Procedure Errors and Messages Manual.

102

SUPER.SUPER required to start ZTILT filename.

filename

is the ZTILT object file.

Cause The ZTILT object file was not owned by the super ID (255, 255). The ZTILT object file must be owned by the super ID (255, 255) in order to successfully load ZTILT and its public shared run‑time libraries (SRLs).

Effect ZTILT process creation is terminated, and no public SRLs are loaded.

Recovery Ensure that the ZTILT object file is owned by the super ID (255, 255), then reload the system or processor.

103

File Error file‑error while attempting to create ZTILT environment.

file‑error

specifies the file‑system error that occurred.

Cause A file‑system error occurred while the ZTILT program environment was being created.

Effect ZTILT process creation is terminated, and no public shared run‑time libraries (SRLs) are loaded.

Recovery Examine the file‑system error to determine the cause of the problem and correct it. For example, file‑system error 11, indicating that the ZTILT file was not found, might have been encountered because ZTILT was not placed in the cold‑load SYSnn subvolume. See Appendix B, for a description of the given error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

Check to make sure that the appropriate ZTILT program file has been placed in the $SYSTEM.SYSnn subvolume you are loading from and that your installation procedures have been followed completely.

If the error persists after correcting the situation, contact your service provider and provide all relevant information as follows:

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated, including SRL message 122

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

104

ZTILT program file either does not have an ELF structure or does not have a 700 file code: filename OBJ GMT: modstamp EOF: eof.

`filename`	identifies the ZTILT program file.
`modstamp`	is the modification timestamp of the ZTILT file in Greenwich mean time (GMT).
`eof`	indicates the end‑of‑file value for the ZTILT file.

Cause The indicated ZTILT program file is not an executable native object file (a file in the ELF format). The filecode is not 700, or the file is internally corrupt.

Effect ZTILT process creation is terminated, and no public shared run‑time libraries (SRLs) are loaded.

Recovery Check to make sure that the appropriate ZTILT program file has been placed in the $SYSTEM.SYSnn subvolume you are loading from and that your installation procedures have been followed completely.

If the error persists after correcting the situation, the ZTILT program file is unusable. Contact your service provider and provide all relevant information as follows:

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

105

File Error file‑error positioning or reading ZTILT program file filename OBJ GMT: modstamp EOF: eof.

`file‑error`	is the file‑system error that occurred.
`filename`	identifies the ZTILT program file.
`modstamp`	is the modification timestamp of the ZTILT file in Greenwich mean time (GMT).
`eof`	indicates the end‑of‑file value for the ZTILT file.

Cause A file‑system error occurred while accessing the indicated ZTILT program file.

Effect ZTILT process creation is terminated, and no public shared run‑time libraries (SRLs) are loaded.

Recovery Ensure that the specified program file is the ZTILT program file, and install the correct program file if it is not. See Appendix B, for a description of the error that occurred. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

If the error persists, the ZTILT program file is probably corrupted. Contact your service provider and provide all relevant information as follows:

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

106

Memory error memcode attempting to obtain global system memory.

memcode

specifies the internal memory error that occurred.

Cause An internal error occurred in an attempt to obtain memory for ZTILT’s shared run‑time libraries (SRLs).

Effect ZTILT process creation is terminated, and no public SRLs are loaded.

Recovery This is an internal system error. Contact your service provider and provide all relevant information as follows:

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated, including SRL message 122
Supporting documentation such as trace files and a processor dump

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

107

SRL data was not found or is not correct in ZTILT program file filename OBJ GMT: modstamp EOF: eof.

`filename`	identifies the ZTILT program file.
`modstamp`	is the modification timestamp of the ZTILT file in Greenwich mean time (GMT).
`eof`	indicates the end‑of‑file value for the ZTILT file.

Cause The indicated ZTILT program file does not have any entries in its internal PUBLIC_SRL_NAMES table.

Effect ZTILT process creation is terminated, and no public shared run‑time libraries (SRLs) are loaded.

Recovery Ensure that the program file is the ZTILT program file, and install the correct program file if it is not.

If the error persists, the ZTILT program file is probably corrupt. Contact your service provider and provide all relevant information as follows:

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

108

Located SRL#tiltnum srlname filename OBJ GMT: modstamp EOF: eof EXDIGEST: export‑digest.

`tiltnum`	is the shared run‑time library’s (SRL’s) tilt number in the ZTILT SRL table.
`srlname`	is the SRL name.
`filename`	is the file name of the SRL.
`modstamp`	is the modification timestamp of the SRL file in Greenwich mean time (GMT).
`eof`	indicates the end‑of‑file value for the SRL file.
`export‑digest`	is the export digest of the SRL.

Cause ZTILT successfully located a public SRL that it refers to.

Effect ZTILT continues locating all public SRLs that it refers to.

Recovery Informational message only; no corrective action is needed.

109

Failure opening SRL file filename. File Error file‑error.

`filename`	is the name of the SRL file.
`file‑error`	indicates the file‑system error that occurred.

Cause A file‑system error occurred while attempting to open the indicated shared run‑time library (SRL).

Effect ZTILT process creation is terminated, and no public SRLs are loaded.

Recovery Ensure that the object file is actually the required SRL object file, and install the correct object file if it is not. See Appendix B, for a description of the error that occurred. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

If the error persists after correcting the situation, the SRL object file is unusable. Contact your service provider and provide all relevant information as follows:

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

110

File Error file‑err constructing name of SRL object file filename.

`file‑err`	is the file‑system error that occurred.
`filename`	specifies the shared run‑time library (SRL) object file.

Cause A file‑system error occurred while trying to locate the SRL or construct its name.

Effect ZTILT process creation is terminated, and no public shared run‑time libraries (SRLs) are loaded.

Recovery Ensure that the object file is the required SRL object file, and install the correct object file if it is not. See Appendix B, for a description of the error that occurred. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

If the error persists after correcting the situation, the SRL object file is unusable. Contact your service provider and provide all relevant information as follows:

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

111

SRL file either does not have ELF structure or does not have a 700 file code: filename OBJ GMT: modstamp EOF: eof.

`filename`	indicates the shared run‑time library (SRL) file.
`modstamp`	is the modification timestamp of the SRL file in Greenwich mean time (GMT).
`eof`	indicates the end‑of‑file value for the SRL file.

Cause The indicated SRL file is not an executable native object file (a file in the ELF format). Either the filecode is not 700, or the file is internally corrupt.

Effect ZTILT process creation is terminated, and no public SRLs are loaded.

If the error persists after correcting the situation, the SRL object file is unusable. Contact your service provider and provide all relevant information as follows:

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

112

File Error file‑error positioning or reading SRL file filename.

`file‑error`	indicates the file‑system error that occurred.
`filename`	identifies the shared run‑time library (SRL) file.

Cause A file‑system error occurred while trying to locate a position within the indicated SRL.

Effect ZTILT process creation is terminated, and no public SRLs are loaded.

Recovery Check to make sure that the appropriate SRL object file has been placed in the $SYSTEM.SYSnn subvolume you are loading from and that your installation procedures have been followed completely. See Appendix B, for a description of the error that occurred. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

If the error persists after correcting the situation, the SRL object file is unusable. Contact your service provider and provide all relevant information as follows:

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

113

File header does not contain the TANDEM_INFO section in SRL file filename OBJ GMT: modstamp EOF: eof.

`filename`	identifies the shared run‑time library (SRL) object file.
`modstamp`	is the modification timestamp of the SRL file in Greenwich mean time (GMT).
`eof`	indicates the end‑of‑file value for the SRL file.

Cause The indicated SRL object file does not contain an executable native object (ELF) TANDEM_INFO section.

Effect ZTILT process creation is terminated, and no public SRLs are loaded.

If the error persists after correcting the situation, the SRL object file is unusable. Contact your service provider and provide all relevant information as follows:

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

114

SRL name (srlname) in filename did not match name expected by ZTILT (srl‑expected).

`srlname`	is the shared run‑time library (SRL) name that ZTILT was linked to.
`filename`	is the object file name of the SRL.
`srl‑expected`	is the name of the SRL that ZTILT was expecting.

Cause The name of an SRL that ZTILT was linked to was not found in the indicated SRL when ZTILT process creation was attempted.

Effect ZTILT process creation is terminated, and no public SRLs are loaded.

Recovery This is an internal error. Contact your service provider and provide all relevant information as follows:

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated, including SRL message 122

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

115

SRL: srlname‑next is not alphabetically greater then previous SRL: srlname‑prev in ZTILT filename PUBLIC_SRL_NAMES.

`srlname‑next`	is a shared run‑time libraries (SRL) name in the ZTILT SRL table.
`srlname‑prev`	is the SRL name that is listed previous to `srlname‑next` in the ZTILT SRL table.
`filename`	is the ZTILT object file.

Cause The ZTILT internal PUBLIC_SRL_NAMES table is out of alphabetical sequence.

Effect ZTILT process creation is terminated, and no public SRLs are loaded.

Recovery This is an internal error. Contact your service provider and provide all relevant information as follows:

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated, including SRL message 122

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

116

File is not an SRL: filename OBJ GMT: modstamp EOF: eof.

`filename`	identifies the shared run‑time library (SRL) object file.
`modstamp`	is the modification timestamp of the SRL file in Greenwich mean time (GMT).
`eof`	indicates the end‑of‑file value for the SRL file.

Cause The indicated SRL object file was not built as an SRL.

Effect ZTILT process creation is terminated, and no public SRLs are loaded.

If the error persists after correcting the situation, the SRL object file is unusable. Contact your service provider and provide all relevant information as follows:

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

117

Failure starting ZTILT. Process_Create_ error pc‑error, error detail err‑detail.

`pc‑error`	indicates the PROCESS‑CREATE_ error that occurred.
`err‑detail`	is the error detail code for the PROCESS_CREATE_ error.

Cause A PROCESS_CREATE_ error occurred in attempting to create the ZTILT process.

Effect ZTILT process creation is terminated, and no public shared run‑time libraries (SRLs) are loaded.

Recovery Other ZTILT operator messages should precede this one. Examine these messages and perform the recovery steps indicated for them. See Appendix D, for a brief description of the specified error. For more detailed information including recovery actions, see Guardian Procedure Errors and Messages Manual.

If the PROCESS_CREATE_ occurs on a subsequent system or processor load after performing the error recovery indicated for the preceding SRL events, contact your service provider and provide all relevant information as follows:

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated, including SRL message 122
Supporting documentation such as trace files and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

118

Public SRLs are successfully loaded.

Cause The ZTILT process has successfully been created and all public shared run‑time libraries (SRLs) are successfully loaded.

Effect All public SRLs are available for use.

Recovery Informational message only; no corrective action is needed. You may now start applications that use public SRLs.

119

While searching for processes with the program name ZTILT, ZTILT encountered error file‑error, error detail error‑detail.

`file‑error`	specifies the file‑system error that occurred.
`error‑detail`	is a PROCESS_GETINFOLIST_ error that provides detail on the file‑system error.

Cause An attempt was made to start a second ZTILT process in the same processor.

Effect The second ZTILT process terminates.

Recovery Run LTILT to determine if there are any SRLs. If there are SRLs, this is an informational message only; no corrective action is needed. The original ZTILT process and all of its related public shared run‑time libraries (SRLs) remain unaffected.

If running LTILT shows that there are no SRLs, investigate the file‑system error. See Appendix B, for a description of the given error. For more detailed information including recovery actions, see Guardian Procedure Errors and Messages Manual. If you cannot resolve the problem, contact your service provider and provide all relevant information as follows:

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated, including SRL message 122
Supporting documentation such as trace files and a processor dump

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

120

While opening $RECEIVE, program file ZTILT encountered error fo‑error.

fo‑error

specifies the FILE_OPEN_ error that occurred.

Cause The ZTILT process encountered a FILE_OPEN_ error when it attempted to open $RECEIVE.

Effect The ZTILT process terminates.

Recovery This is an internal error. Contact your service provider and provide all relevant information as follows:

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated, including SRL message 122
Supporting documentation such as trace files and a processor dump

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

121

File header does not contain the TANDEM_GINFO section in SRL file filename OBJ GMT:modstamp EOF: eof.

`filename`	indicates the shared run‑time library (SRL) object file.
`modstamp`	is the modification timestamp of the SRL file in Greenwich mean time (GMT).
`eof`	indicates the end‑of‑file value for the SRL file.

Cause The indicated SRL object file does not contain an executable native object (ELF) TANDEM_GINFO section.

Effect ZTILT process creation is terminated, and no public SRLs are loaded.

If the error persists after correcting the situation, the SRL object file is unusable. Contact your service provider and provide all relevant information as follows:

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

122

Located ZTILT filename OBJ GMT: modstamp EOF: eof.

`filename`	indicates the ZTILT object file.
`modstamp`	is the modification timestamp of the ZTILT file in Greenwich mean time (GMT).
`eof`	indicates the end‑of‑file value for the ZTILT file.

Cause The indicated ZTILT object file was successfully located.

Effect Processing of the ZTILT object file continues. Shared run‑time library (SRL) loading is attempted.

Recovery Informational message only; no corrective action is needed.

123

No GINFO section in ZTILT program file filename OBJ GMT: modstamp EOF: eof.

`filename`	identifies the ZTILT program file.
`modstamp`	is the modification timestamp of the ZTILT file in Greenwich mean time (GMT).
`eof`	indicates the end‑of‑file value for the ZTILT file.

Cause The indicated ZTILT program file does not contain a GINFO section in its internal PUBLIC_SRL_NAMES table.

Effect ZTILT process creation is terminated, and no public shared run‑time libraries (SRLs) are loaded.

Recovery Ensure that the program file is actually the ZTILT program file, and install the correct program file if it is not.

If the error persists, the ZTILT program file is probably corrupted. Contact your service provider and provide all relevant information as follows:

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

124

ZTILT filename OBJ GMT: modstamp EOF: eof Not Linked to Any TILT SRLs.

`filename`	identifies the ZTILT object file.
`modstamp`	is the modification timestamp of the ZTILT file in Greenwich mean time (GMT).
`eof`	indicates the end‑of‑file value for the ZTILT file.

Cause The indicated ZTILT object file is not linked to any public shared run‑time libraries (SRLs).

Effect ZTILT process creation is terminated, and no public SRLs are loaded.

Recovery Ensure that the object file is actually the ZTILT object file, and install the correct object file if it is not.

If the error persists, the ZTILT object file is probably corrupted. Contact your service provider and provide all relevant information as follows:

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

125

ZTILT Linked to TILT SRL srlname but the SRL is not defined in ZTILT PUBLIC_SRL_NAMES: ZTILT ztiltname OBJ GMT: modstamp EOF: eof.

`srlname`	identifies the shared run‑time library (SRL).
`ztiltname`	identifies the ZTILT object file.
`modstamp`	is the modification timestamp of the ZTILT file in Greenwich mean time (GMT).
`eof`	indicates the end‑of‑file value for the ZTILT file.

Cause ZTILT was linked to a shared run‑time library (SRL) that was not defined in its internal PUBLIC_SRL_NAMES table.

Effect ZTILT process creation is terminated, and no public SRLs are loaded.

Recovery Ensure that the object file is actually the ZTILT object file, and install the correct object file if it is not.

If the error persists, the ZTILT object file is probably corrupted. Contact your service provider and provide all relevant information as follows:

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

126

ZTILT PUBLIC_SRL_NAMES defines SRL srlname: a) ZTILT is NOT linked to the SRL with NLD; b) the SRL's version procedure is NOT exported to ZTILT: ZTILT filename OBJ GMT: modstamp EOF: eof.

`srlname`	specifies the shared run‑time library (SRL) name that ZTILT referenced.
`filename`	specifies the ZTILT object file.
`modstamp`	is the modification timestamp of the ZTILT file in Greenwich mean time (GMT).
`eof`	indicates the end‑of‑file value for the ZTILT file.

Cause The indicated SRL is defined in the internal ZTILT PUBLIC_SRL_NAMES table, but ZTILT is not linked to it with NLD, the native mode linker, or the SRL’s version is not exported to ZTILT.

Effect ZTILT process creation is terminated, and no public SRLs are loaded.

Recovery Ensure that the object file is actually the ZTILT object file, and install the correct object file if it is not.

If the error persists, the ZTILT object file is probably corrupted. Contact your service provider and provide all relevant information as follows:

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

127

Failure opening ZTILT file filename. File Error file‑error.

`filename`	identifies the ZTILT object file.
`file‑error`	indicates the file‑system error that occurred.

Cause A file‑system error occurred accessing the indicated ZTILT object file.

Effect ZTILT process creation is terminated, and no public shared run‑time libraries (SRLs) are loaded.

Recovery Examine the file‑system error and the specified ZTILT object file to determine the cause of the error and attempt to correct the problem. See Appendix B, for a description of the given error. For more detailed information including recovery actions, see Guardian Procedure Errors and Messages Manual. Locate the ZTILT object file, install it, and reload the system or processor.

If the error persists, contact your service provider and provide all relevant information as follows:

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated, including SRL message 122

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

128

SUPER.SUPER access required for SRL object object‑file.

object‑file

is the public shared run‑time library (SRL) object file.

Cause The public SRL object file was not owned by the super ID (255, 255). The public SRL object file must be owned by the super ID (255, 255) in order to successfully load public SRLs.

Effect ZTILT process creation is terminated, and no public SRLs are loaded.

Recovery Ensure that the public SRL object file is owned by the super ID (255, 255), then reload the affected system or processor.

129

Public SRLs are successfully loaded in partial error recovery mode.

Cause Some public SRLs were not loaded.

Effect The SRLs that were not loaded are not available.

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated, including SRL message 122
Supporting documentation such as trace files and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

130

SRL removed from PUBLIC SRL cache File error fecode, Event event, Process_Create_ error errorcode, error detail errordetail.

`fecode`	is the file-system error code.
`errorcode`	is the PROCESS_CREATE_ error that occurred.
`errordetail`	is the error detail code for the PROCESS_CREATE_ error that occurred.

Cause An error that occurred while loading another SRL caused the loading of the SRL in this event to fail.

Effect The specified SRLs are not available.

Recovery This is an informational message only; no corrective action is needed. This event follows event 129.

131

No RLD was loaded. PIC programs cannot be run.

Cause No ZRLDREL file was included in the set of public SRLs installed on this system. The file might not have been included in the installation, or the ZTILT and public SRL files might have been copied from an older system.

Effect No run-time loader (RLD) is loaded; therefore, PIC programs will not be able to run.

Recovery Make sure that the appropriate ZTILT object file and all the appropriate SRL object files (specifically ZRLDREL) have been placed in the $SYSTEM.SYSnn subvolume you are loading from and that installation procedures have been followed correctly.

If the error persists after you correct problem, and you intend to run PIC programs on your system, contact your service provider and provide all relevant information as follows:

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

132

count of the loaded SRLs are not hybrids. Some PIC programs and DLLs may not run.

count

is the is the number of non-hybrid SRLs.

Cause One or more of the public SRLs installed on this system is not a hybrid SRL.

Effect Any PIC programs or DLLs that require the use of a public SRL will be unable to run if that SRL is not a hybrid SRL.

Recovery Make sure that the appropriate ZTILT object files and all the appropriate object files (specifically ZRLDSRL) have been placed in the SYSTEM.SYSnn subvolume you are loading from and that installation procedures have been followed correctly.

If the error persists after you correct problem, and you intend to run PIC programs on your system, contact your service provider and provide all relevant information as follows:

Event Management Service (EMS) logs
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.