Chapter 77 PAM Messages

Cause   PAMMAN encountered an internal error.

Effect  The PAMMAN primary process might change to the backup process.

Recovery  This is a serious error. Contact your service provider.

Cause  PAMMAN encountered an internal error.

Effect  The PAMMAN primary process might change to the backup process.

Recovery  This is a serious error. Contact your service provider.

Cause  The PAMMAN backup process started.

Effect  PAMMAN is running as a NonStop process pair.

Recovery  None. This is an informational event.

Cause  The PAMMAN primary process could not start the backup process. The processor in which PAMMAN is attempting to start the backup process might not be started.

Effect  PAMMAN is not running as a NonStop process pair.

Recovery  Start the processor in which PAMMAN is attempting to start the backup process.

Cause  PAMMAN could not create a backup process although the processor in which it is attempting to start the process is up.

Effect  PAMMAN does not run as a NonStop process pair.

Recovery  Switch the backup process to a different processor. See the SCF Reference Manual for the Kernel Subsystem for information about how to switch a manager process to another processor.

Cause  The PAMMAN primary process was unable to create a checkpoint with the backup process.

Effect  The PAMMAN backup process does not have current information.

Recovery  If this error persists, abort and then restart the PAMMAN process. See the SCF Reference Manual for the Kernel Subsystem for information on aborting and starting a manager process.

Cause  PAMMAN could not create a PAM Monitor (PAMMON) process.

Effect  A PAMMON process in one of the processors is not running.

Recovery  Abort and then restart PAMMAN. See the SCF Reference Manual for the Kernel Subsystem for information on aborting and starting a manager process.

Cause  PAMMAN is unable to add an object into its name-space, because:

Effect  The object is not added. The operation continues, but there is a possible name‑space inconsistency between PAM and PAMMAN.

Recovery  Stop and restart PAMMAN. If the problem doesn't go away, contact your support representative and provide all relevant information as follows:

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.

Cause  PAMMAN is unable to delete an object from its name-space because the name of the object is not found.

Effect  The object is not deleted. The operation continues, but there is a possible name‑space inconsistency between PAM and PAMMAN.

Recovery  Stop and restart PAMMAN. If the problem doesn't go away, contact your support representative and provide all relevant information as follows:

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.

Cause  The message PAMMAN received through QIO Global Queue contains an object name with a bad file-system naming format.

Effect  The message is discarded. The operation continues, but possible name-space inconsistency between PAM and PAMMAN.

Recovery  Stop and restart PAMMAN. If the problem doesn't go away, contact your support representative and provide all relevant information as follows:

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.

Cause  PAMMAN received a bad MD while listening to the QIO Global Queue.

Effect  Possible name-space inconsistency between PAM and PAMMAN.

Recovery  Stop and restart PAMMAN. If the problem doesn't go away, contact your support representative and provide all relevant information as follows:

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.

Cause  PAMMAN detects an error while doing a QIO library operation.

Effect  This is a serious internal error. Depending on the QIO function performed, PAMMAN may or may not be able to continue operation.

Recovery  Contact your support representative and provide all relevant information as follows:

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.

Cause   PAM process is not responding properly to the FILE_OPEN_ call.

Effect  PAMMAN cannot open the PAM process. No SCF requests can be forwarded to that PAM process.

Recovery   Stop and restart the PAMMAN process. If this error persists, contact your service provider and provide all relevant information as follows:

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.

Cause  An inbound aggregate SDU was delivered to the port module but could not be delivered to a client (user of a port module).

Effect  The inbound aggregate SDU is discarded, and the error is recorded in the port’s statistics.

Recovery  If the aggregate SDU could not be delivered to the application, the subsystem is able to deliver aggregate SDUs faster than the client can post file-system reads. The client should increase the number of SDUs in the inbound aggregate SDU by means of the ALTER PORT command’s data forward count (DFC) attribute, which slows the rate that aggregate SDUs are delivered to the application.

If the aggregate SDU contained a bad address, the adapter has delivered an aggregate SDU to an unknown port. Data may be lost, and the client may have to perform higher‑level protocol. Contact your support representative and provide all relevant information as follows:

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.

Cause  The client has delivered an aggregate SDU to the subsystem that does not conform to the rules governing the format of these messages.

Effect  The adapter discards all remaining frames in the erroneous aggregate SDU message. SDUs previously taken from the message are not affected and are delivered to the media.

Recovery  The client should isolate the bad message, determine where it deviates from the proper format, and fix the offending code. If the client is using the ZL2S formatting library, contact your support representative and provide all relevant information as follows:

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.

Cause  The backup process cannot process a checkpoint.

Effect  No immediate problems result, but a switch can result in unpredictable actions by PAM.

Recovery  Halt and dump the processor of the PAM backup process, then reload.

If the problem persists, do not reload the backup; contact your support representative and provide all relevant information as follows:

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.

Cause  The LIF associated with the PAM process either switched ownership from the current primary or it no longer has access on this processor.

Effect  PAM waits for the LIF to come up on the new processor and registers the ports. The application data transfer resumes. If the LIF switches processors again, PAM follows the LIF.

Recovery  If the PAM process keeps switching or does not recover, check the status of the associated LIF and PIF by using PFPFMON commands and change the access of the LIF to the processor you want. Bring up the LIF and PIF if they are down.

Cause  The operator stopped the line with a Subsystem Control Facility (SCF) command, or it stopped itself because of a serious error.

Effect  The line is stopped.

Recovery  If the error was not forced by an ABORT or PFSTOP command, contact your support representative and provide all relevant information as follows:

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.

Cause  The operator successfully returned the device to the system through a Subsystem Control Facility (SCF) START command.

Effect  Processing continues normally.

Recovery  Informational message only; no corrective action is needed.

Cause  PAM has detected a serious internal error. This error is generated at the point PAM detected the error.

Effect  Subsequent requests to the line are rejected with file-system error 157.

Recovery  Halt and dump the processor of the reporting process, then reload. Contact your support representative and provide all relevant information as follows:

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.

Cause  The PAM process detected an error at process initialization time and is unable to go on.

Effect  PAM terminates abnormally.

Recovery  Restart PAM with the correct values. If it still fails, contact your support representative and provide all relevant information as follows:

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.

Cause  A problem was encountered during communication with the adapter during the start/stop port phase.

Effect  The port stays in the stopped state.

Recovery  Recovery depends on the type of problem. If this message is followed by the message “Port Configuration Failed (PAM:18)”, the port has not entered the started state. Issue the START command again.

If the problem persists, contact your support representative and provide all relevant information as follows:

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.

Cause  This message is generated if PAM could not configure a port. This error should be preceded by a port configuration error.

Effect  The port stays in the stopped state.

Recovery  Recovery depends on the type of problem. Issue the START command again.

If the problem persists, contact your support representative and provide all relevant information as follows:

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.

Cause  The PAM makes extensive use of state machines. This message is generated if the PAM process detects an internal state-machine error.

Effect  The subsystem’s action depends on the entity that reported the error. If one of the PORT SAPs or the other entities reports the problem, that entity is put in the STOPPED state but the rest of the subsystem functions normally.

Recovery  Reconfigure the object and continue operation.

Contact your support representative and provide all relevant information as follows:

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.

Cause  An unexpected line operation (LIOP) response was received by the I/0 process.

Effect  The LIOP frame is discarded. The operation continues; however, requests might be lost as the result of this error.

Recovery  Contact your support representative and provide all relevant information as follows:

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.

Cause  The cause of this error is described in not-notif-cause.

Recovery  Loss of notifications to the SNAX line-handler process generally results in SNAX timing out and reestablishing the session. When a Link_Failed or a Window_Exceeded error is received, SNAX should reopen the SAP and reestablish the session.

If the Out_of_Memory or Window_Exceeded error is temporary, subsequent notifications will be delivered and no action is necessary. However, if these errors are not temporary, you should contact your support representative and provide all relevant information as follows:

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.

Cause  The cause of this error is described in not-sent-cause.

Recovery  If the cause of the error is LIF Failed, SNAX is able to reestablish the session when the LIF comes up; no action is necessary. If the cause of the error is Read Link Failed, you should contact your support representative and provide all relevant information as follows:

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.

Cause  The PAM backup process cannot start.

Effect  The backup PAM process is not created. The primary process continues to run and tries to restart the backup until the backup process starts.

Recovery  If the problem persists, contact your support representative and provide all relevant information as follows:

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.

Cause  The cause depends on the notif-func and notif-err.

Effect  PAM continues to run but the error could affect data transfer.

Recovery  If the PAM process does not recover or the data transfer does not continue, using SCF, check and log the STATUS, INFO and STATISTICS of the PAM line and its subordinate objects as well as the STATUS of the associated LIF, PIF and SAC objects.

If the LIF and PIF are STOPPED or the PAM's primary and backup processor are not in the LIF access list, determine why the access changed, and alter the access list to PAM's primary and backup processor; or restart PAM on the processors that have access to the LIF.

If LIF and the LIF access are OK, take an online processor dump of the primary and backup processors and abort and restart the PAM process. If you still have problems, contact your service provider with the processor dumps and the SCF and EMS logs.