Chapter 22 DLL (Dynamic Link Library) Messages

The messages in this chapter are generated by the ZDLL subsystem on H-series systems during the preloading of public DLLs while starting the processor. The subsystem ID displayed by these messages includes ZDLL as the subsystem name.




	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.

A set of public DLLs includes the DLLs and these files:

File	Description
ZREG	Describes the DLLs and ZIMPIMP
ZREGPTR	Designates the ZDLL`rrr` subvolume
ZIMPIMP	Describes entry points in the implicit DLLs

Ordinarily, DSM/SCM runs a system generation program (if necessary) which:

Creates a new system load subvolume (SYSnn), which includes ZIMPIMP.
Runs the PLINSTL utility, which adjusts symbol bindings in the DLLs and generates ZREG.
ZREG and the DLLs go on the DLL subvolume, ZDLLrrr (where rrr is generated by DSM/SCM).
Creates the ZREGPTR file in SYSnn.

When you perform a system load or reload a processor, the operating system preloads the public DLLs by reading ZREGPTR, ZREG, and the designated DLLs. The events in this chapter are generated in the preload operation.

100

file-system-call error on file-name. [ File system error error-code ] [ info-string ]

file-system-call

is either the name of a file system call (for example, FILE_OPEN_ or FILE_GETINFOLIST_) or it is empty.

file-name

is the fully qualified name of either the ZREG file or the ZREGPTR file.

error-code

is the file system error code.

info-string

is a string that describes the error. For example:

Not a filecode 180 file.
Not an odd-unstructured disk file

Cause An error occurred while opening or attempting to open file-name.

Effect No public DLLs are loaded (as message 110 reports). The processor halts with halt code %5030.

Recovery If the problem occurred while coldloading, revert to a previously working system image (SYSnn and ZDLLrrr subvolumes).

If you modified file-name, revert to the original file and reboot the system.

Otherwise, recovery depends on the file-system error that error-code or info-string specifies. If that file-system error seems implausible and uncorrectable, bring the system up on another SYSnn subvolume and report the problem to your service provider with this information:

Events Management Service (EMS) logs
Description 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):
- Your system number
- Numbers and versions of all related products

101

No required-public-DLL-name was loaded. file-type programs cannot be run.

required-public-DLL-name

is the name of the required public DLL, which is either:

Runtime loader (ZRLDDLL)
TNS Emulator (ZTNSDLL)

file-type

is the file type supported by the required public DLL:

required-public-DLL-name	file-type Supported
ZRLDDLL	PIC
ZTNSDLL	TNS

Cause Either:

required-public-DLL-name was not specified in the ZREG file.
required-public-DLL-name was specified incorrectly in the ZREG file (as message 107 might report).
An error (which message 102 reports) occurred while preloading required-public-DLL-name .

Effect required-public-DLL-name is not preloaded. Files of type file-type cannot run on this processor. The processor halts with halt code %5030, %5031, %5032, or %5033.

Recovery If the problem occurred while coldloading, revert to a previously working system image (SYSnn and ZDLLrrr subvolumes).

If you modified the ZREGPTR file, the ZREG file, or required-public-DLL-name, revert to the original files and reboot the system.

If you are using unmodified ZREGPTR and ZREG files that DSM/SCM installed, and required-public-DLL-name is in the DLLS subvolume, report the problem to your service provider with this information:

Events Management Service (EMS) logs
Description 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):
- Your system number
- Numbers and versions of all related products

102

Public DLL file file-name preload failed: process creation error pc-error, detail pc-err-detail. [ Export digest mismatched: expected expected-digest, ] [ found found-digest. ] [ Export digest missing in zreg file. ] [ Warning: timestamp-type timestamp missing in ZREG file. ] [ Warning: timestamp-type timestamp mismatched: expected ] [ expected-timestamp, found found-timestamp. ]




	NOTE: Warnings appear in this message only if errors occurred also. If only warnings occurred, message 103 displays them.

`file-name`	is the name of the public DLL that failed to preload.
`pc-error`	is the process-creation error that caused the failure. For information about process-creation errors, see the Guardian Procedure Errors and Messages Manual.
`pc-err-detail`	is the process-creation error detail. For information about process-creation errors, see the Guardian Procedure Errors and Messages Manual.
`expected-digest`	is the export digest that the ZREG file specifies for `file-name`.
`found-digest`	is the actual export digest for `file-name`.
`timestamp-type`	is one of these timestamp types: link update mod (“mod” means “modification”)
`expected-timestamp`	is the timestamp that the ZREG file specifies for `file-name` for the `timestamp-type` timestamp.
`found-timestamp`	is the actual timestamp for `file-name`for the `timestamp-type` timestamp.

Cause See pc-error and pc-err-detail. (Missing and mismatched timestamps are warnings, which indicate that file-name might not be the public DLL that the ZREG file specifies.)

Effect file-name is not preloaded and cannot be used by programs and DLLs that require it.

Recovery If you modified the ZREGPTR file, the ZREG file, or file-name, revert to the original files and reboot the system.

If you are using unmodified ZREGPTR and ZREG files that DSM/SCM installed, and file-name is in the DLLS subvolume, report the problem to your service provider with this information:

Events Management Service (EMS) logs
Description 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):
- Your system number
- Numbers and versions of all related products

103

Public DLL file file-name preload-success-string. [ Warning: timestamp-type timestamp missing in ZREG file. ] [ Warning: timestamp-type timestamp mismatched: expected ] [ expected-timestamp, found found-timestamp. ]

file-name

is the name of the public DLL.

preload-success-string

is a string that reports the status of file-name, which is either:

preloaded successfully
preloaded but discarded (DLL count too small)

timestamp-type

is one of these timestamp types:

link
update
mod

(“mod” means “modification”)

expected-timestamp

is the timestamp that the ZREG file specifies for file-name for the timestamp-type timestamp.

found-timestamp

is the actual timestamp for file-namefor the timestamp-type timestamp.

Cause If the value of preload-success-string is preloaded successfully, then file-name preloaded without errors.

If the value of preload-success-string is preloaded but discarded (DLL count too small), then the dll_count that the ZREG file specifies for file-name is too small.

If a timestamp is missing, the ZREG file was modified by means other than normal installation.

If a timestamp is mismatched, either:

The file-name in the DLLS subvolume is a different copy of file-name that has the same entry-point addresses (an export digest mismatch would cause an error).
The ZREG file was replaced.
The timestamp entry was modified.

Effect If preload-success-string is preloaded successfully, file-name can be used by programs and DLLs that require it.

If preload-success-string is preloaded but discarded (DLL count too small), file-name is not preloaded and cannot be used by programs and DLLs that require it. Message 106 reports the number of discarded entries.

Recovery If preload-success-string is preloaded but discarded (DLL count too small), increase dll_count in the ZREG file by at least the number of discarded entries that message 106 reported.

If a timestamp is missing, revert to the original ZREG file.

If a timestamp is mismatched, revert to the original ZREG file and file-name.

If a PLINSTL-generated ZREG file results in discarded public DLLs, report the problem to your service provider with this information:

Events Management Service (EMS) logs
Description 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):
- Your system number
- Numbers and versions of all related products

104

Implicit_import statement not found in zreg.

Cause The ZREG file is faulty.

Effect No public DLLs are loaded (as message 110 reports). The processor halts with halt code %5030.

Recovery If the problem occurred while coldloading, revert to a previously working system image (SYSnn and ZDLLrrr subvolumes).

If you modified the ZREG file, revert to the original file and reboot the system.

If this error occurs with the original ZREGPTR and ZREG files that DSM/SCM installs, report the problem to your service provider with this information:

Events Management Service (EMS) logs
Description 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):
- Your system number
- Numbers and versions of all related products

105

Problems seen in implicit_import statement. { Export digest mismatched: expected expected-digest, found } { found-digest. } { } { Export digest missing in zreg file. } [ Warning: timestamp-type timestamp missing in ZREG file. ] [ Warning: timestamp-type timestamp mismatched: expected ] [ expected-timestamp, found found-timestamp. ]

`expected-digest`	is the export digest that the ZREG file specifies for the ZIMPIMP file.
`found-digest`	is the actual export digest for the ZIMPIMP file.
`timestamp-type`	is one of these timestamp types: link update mod (“mod” means “modification”)
`expected-timestamp`	is the timestamp that the ZREG file specifies for the ZIMPIMP file for the `timestamp-type` timestamp.
`found-timestamp`	is the actual timestamp for the ZIMPIMP file for the `timestamp-type` timestamp.

Cause Either:

The ZREG file’s implicit_import statement specified an export digest that did not match the export digest of the ZIMPIMP file that was loaded for the processor.
The ZREG file’s implicit_import statement did not specify an export digest.

Indirect causes of the preceding direct causes are:

The wrong ZREG file was used with this SYSnn subvolume.
The implicit_import statement was modified.
The ZIMPIMP file loaded in the SYSnnsubvolume was replaced.

If a timestamp is missing or mismatched, the ZREG file was probably either modified or replaced.

Effect If the message contains only warnings, the processor initialization continues. Otherwise, no public DLLs are loaded (as message 110 reports) and the processor halts with halt code %5030.

Recovery If the message contains only warnings, no recovery is required. If the problem occurred while coldloading, revert to a previously working system image (SYSnn and ZDLLrrr subvolumes).

If you modified the ZREGPTR, ZREG, or ZIMPIMP file installed by DSM/SCM, revert to the original files and reboot the system.

If this error occurs with the original ZREGPTR, ZREG, and ZIMPIMP files that DSM/SCM installs, report the problem to your service provider with this information:

Events Management Service (EMS) logs
Description 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):
- Your system number
- Numbers and versions of all related products

106

num-loaded public DLLs are successfully loaded. [ Expected DLL count: expected-count, actual count ] [ found: actual-count. ] [ num-failed DLLs failed preload. ] [ good-discards loadable DLLs were discarded. ]

`num-loaded`	is the number of public DLLs that preloaded successfully.
`expected-count`	is the number of public DLLs that the ZREG file specifies. If the ZREG file does not specify the number of public DLLs, `expected-count` is the default number of public DLLs.
`actual-count`	is the number of successfully parsed DLL entries in the ZREG file.
`num-failed`	is the number of public DLLs that failed to preload.
`good-discards`	is the number of preloadable public DLLs that do not have entries in the preload table because the preload table was filled with good entries.

Cause Preloading of public DLLs has completed.

The cause of the optional information

Expected DLL count: expected-count, actual count found: actual-count.

is that the number of public DDLs specified by dll_count in the ZREG file differed from the number of DLL entries found in the ZREG file.

The cause of the optional information

num-failed DLLs failed preload.

is that some public DLLs failed preload.

The direct cause of the optional information

good-discards loadable DLLs were discarded.

is that that some preloadable public DLLs were discarded because the value of dll_count was too small. The indirect cause is that you modified the ZREG file, either adding DLL entries or decreasing the value of dll_count.

If expected-count does not match actual-count, but no good entries were discarded and no public DLLs failed to preload, the cause is either:

Some entries were deleted from the ZREG file.
The dll_count in the ZREG file was modified.

Effect The processor runs with the successfully preloaded public DLLs, unless ZRLDDLL or ZTNSDDL failed to load. If ZRLDDLL or ZTNSDDL failed to load:

Message 101 is issued (once or twice).
The processor halts with halt code %5031, %5032, or %5033.

For each public DLL, either:

Message 102 is issued, reporting the reason that the DLL failed to preload.
Message 103 is issued, reporting either that the DLL preloaded successfully or that it was discarded.
NOTE: The PLINSTL command list is another way to show which public DLLs preloaded successfully.

Recovery If good entries were discarded, increase the value of dll_count in the ZREG file by at least good-discards.)

If any public DLL failed to preload, find the reason in the message 102 for that DLL.

If you modified the ZREG file or the DLLS subvolume, revert to the original files. If not, report the problem to your service provider with this information:

Events Management Service (EMS) logs
Description 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):
- Your system number
- Numbers and versions of all related products

107

Problem found on line line-num column column-num of file-name. [ explanation-line ]...

line-num

is the line number in the file file-name.

column-num

is the column number on the line line-num.

file-name

is the fully qualified name of the file (ZREG or ZREGPTR) in which the error occurred.

explanation-line

is an explanation of the problem. Two examples are:

Warning: Unrecognized or invalid statement name; ignored
dll_count statement not found before the first dll statement 
in zreg. The default default-dll-count is being used.

Cause The direct cause is that file-name contains the specified defect at the specified location. The indirect cause is that you modified file-name.

Effect The entry might not be processed—if it is not, an explanation-line reports this.

Recovery If you modified file-name, revert to the original file. If not, report the problem to your service provider with this information:

Events Management Service (EMS) logs
Description 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):
- Your system number
- Numbers and versions of all related products

108

Internal Preload error internal-error-num. [ The error reported is error-num. ]

`internal-error-num`	is an internal preloading error number.
`error-num`	is an error number that might be associated with `internal-error-num`.

Cause An internal preloading problem. The failure is likely to occur on all processors.

Effect No public DLLs are loaded (as message 110 reports). The processor halts with halt code %5030.

Recovery Coldload another SYSnn subvolume. Report internal-error-num and error-num to your service provider with this information:

Events Management Service (EMS) logs
Description 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):
- Your system number
- Numbers and versions of all related products

109

Warning: File file-name is empty.

file-name

is the fully qualified name of the ZREGPTR file.

Cause The ZREGPTR file was empty.

Effect The SYSnn subvolume is treated as the DLLS subvolume, which is expected to contain the ZREG file and the public DLLs.

Recovery If this situation was intended (that is, you deliberately bypassed DSM/SCM to create a SYSnn subvolume containing the ZREG, public DLLs, and an empty ZREGPTR file), no recovery is necessary.

If this situation was not intended, replace the empty ZREGPTR file (in the SYSnn subvolume) with the DSM/SCM-generated ZREGPTR file. If your DSM/SCM-generated ZREGPTR file is empty, report the problem to your service provider with this information:

Events Management Service (EMS) logs
Description 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):
- Your system number
- Numbers and versions of all related products

110

Error in preload; No public DLLs were loaded.

Cause Reported by a previous event, such as:

Message 100
Message 104
Message 105
Message 108

Effect No public DLLs are loaded. The processor halts with halt code %5030. The failure is likely to occur on all processors.

Recovery If the problem occurred while coldloading, revert to a previously working system image (SYSnn and ZDLLrrr subvolumes).

If you cannot resolve the problems reported by the previous event or events, and if you modified the DLLS subvolume, ZREG file, or ZREGPTR file, then revert to the original files and reboot the system.

If you did not modify these files, or if similar failure occurs with the original files, report the problem to your service provider with this information:

Events Management Service (EMS) logs
Description 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):
- Your system number
- Numbers and versions of all related products

111

Warning: The scan marker was not found in file-name.

file-name

is the fully qualified name of the ZREG file.

Cause The ZREG file was not produced by PLINSTL, which inserts the scan marker.

Effect The ZREG file might not be the expected one, or might have been modified.

Recovery Unless you want to use a modified ZREG file, replace the ZREG file with the original ZREG file that PLINSTL generated for DSM/SCM. If this event occurs with the original ZREG file, report the problem to your service provider with this information:

Events Management Service (EMS) logs
Description 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):
- Your system number
- Numbers and versions of all related products