Chapter 27 DSM/SCM Messages

The messages in this chapter are sent to $ZPHI by DSM/SCM. The subsystem ID displayed by these messages includes DSMSCM 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.

You can view operator messages using the:

Planner Interface, which lets you display the Event Management Service (EMS) messages generated during the processing of a request.
To display the EMS messages for a request on the Planner Interface:
1. Select Requests>Requests list....
2. Select a request name.
3. Select Show EMS events... (or click Status details..., then click Show EMS events...).
Target Interface, which lets you display the EMS messages associated with the current request:
- To display the EMS messages for the current request on the Target Interface, press F4 (Show messages). DSM/SCM displays the Show EMS messages screen.
- To display EMS messages not related to the current request on the Target Interface, press F4 (Show nonrequest-related errors) from the Show EMS Messages screen.

For information on how to obtain details on the OSS error messages listed in this chapter, see the Guardian Procedure Errors and Messages Manual.

Error numbers that appear in DSM/SCM EMS messages are defined in:

Manual	Defines
EMS Manual	Event Management Services (EMS) errors
Guardian Procedure Errors and Messages Manual	File-system errors
SQL/MP Messages Manual	SQL/MP errors
TS/MP Pathsend and Server Programming Manual	PATHSEND errors
Safeguard Management Programming Manual	Safeguard Subsystem Programmatic Interface (SPI) errors
Software Identification (SWID) User’s Guide	Software Archive (SWARC) errors
Guardian Native C Library Calls Reference Manual	P errors and S errors

1000

file-type files(s) is/are located at filename.

file-type

is the type of file whose location is being reported. Typical values returned and the file types they represent are:

Activation package	Target file
Report file	Trace file
System snapshot

For a complete list of possible file-type values, see message 5095.

filename

is the file name in the internal format of the file whose location is being reported.

Cause DSM/SCM has created one or more files of the specified file type.

Effect This message reports the creation of the indicated files and their location.

Recovery Informational message only; no corrective action is needed.

1005

activity-name activity started.

activity-name

is the activity that started. Possible values:

Apply Configuration	IPM Replaces Report Print
Backout Configuration	IPM Requisite Report Disk
Build Configuration	IPM Requisite Report Print
Create Snapshot	IPM Replaces Report Disk
Receive Snapshot	Release Doc Disk
Export Files	Release Doc Print
Get Preview	Softdoc Disk
Host Report Disk	Softdoc Print
Host Report Print	Target Report Disk
Independent Snapshot	Target Report Print
Initial Apply Configuration	User-Defined Report Disk
Initial Build Configuration	User-Defined Report Print
Input Snapshot	Verify Database
Input Software

Cause A DSM/SCM component started the specified activity.

Effect This message reports the start of the activity.

Recovery Informational message only; no corrective action is needed.

1010

activity-name completed completion-code.

activity-name

is the activity that just completed execution by DSM/SCM. Possible values:

Apply Configuration	IPM Replaces Report Print
Backout Configuration	IPM Requisite Report Disk
Build Configuration	IPM Requisite Report Print
Create Snapshot	IPM Replaces Report Disk
Receive Snapshot	Release Doc Disk
Export Files	Release Doc Print
Get Preview	Softdoc Disk
Host Report Disk	Softdoc Print
Host Report Print	Target Report Disk
Independent Snapshot	Target Report Print
Initial Apply Configuration	User-Defined Report Disk
Initial Build Configuration	User-Defined Report Print
Input Snapshot	Verify Database
Input Software

completion-code

is the completion status of the activity. Possible values and the statuses they represent are:

Value	Description
cancelled	Activity completed was cancelled.
with error(s)	Activity completed with errors.
successfully	Activity completed successfully.
with warning(s)	Activity completed with warnings.

Cause DSM/SCM completed the specified activity.

Effect This message reports the completion status of the activity.

Recovery Informational message only; no corrective action is needed.

1015

Snapshot needed for host host-name to correct Apply error. Run Target Interface and select CREATE SNAPSHOT activity.

host-name

is the host name where the error occurred.

Cause An error occurred during an Apply activity. A target system snapshot must be input at the host to synchronize the host and target.

Effect The host cannot complete the Apply activity.

Recovery Run the Target Interface and select the Create Snapshot activity to produce a current system snapshot. Input this snapshot at the host with the Input Snapshot activity and then start a new Build or Build/Apply activity.

1020

activity-name stopped stopped-code.

activity-name

is the activity that stopped. Possible values:

Apply Configuration	IPM Replaces Report Print
Backout Configuration	IPM Requisite Report Disk
Build Configuration	IPM Requisite Report Print
Create Snapshot	IPM Replaces Report Disk
Receive Snapshot	Release Doc Disk
Export Files	Release Doc Print
Get Preview	Softdoc Disk
Host Report Disk	Softdoc Print
Host Report Print	Target Report Disk
Independent Snapshot	Target Report Print
Initial Apply Configuration	User-Defined Report Disk
Initial Build Configuration	User-Defined Report Print
Input Snapshot	Verify Database
Input Software

stopped-code

is the stopped status of the activity. Possible values and the statuses they represent are:

restartable. Correct error, RESTART activity	The DSM/SCM activity stopped because of an error and can be restarted after the error condition is corrected.
non restartable. Correct error, CANCEL activity	The DSM/SCM activity stopped because of an error and cannot be restarted. The activity must therefore be cancelled.
cancelled restartable. Correct error, RESTART activity	A planner or operator cancelled the activity. The activity stopped while it was being cancelled. It can be restarted after the error condition is corrected.
cancelled non restartable. Correct error, CANCEL activity	A planner or operator cancelled the activity. The activity stopped while being cancelled. It cannot be restarted. The activity must therefore be cancelled.

Cause An error during the specified activity caused processing to stop. The error is reported in preceding messages. This message indicates the stopped status of the activity.

Effect Processing stops.

Recovery See the error code returned in the preceding message. For recovery action, see the description of the error in this chapter. If the status is restartable, the operator should correct the error and restart the activity.

If the status is nonrestartable, correct the error and cancel the activity. You can then resubmit the request if necessary.

Use the Maintenance Interface to delete nonrestartable requests. See the DSM/SCM User’s Guide.

1025

Retry count exceeded, PATHMON pmon-name server class server-class-name could not be started. The planner must retry the request.

`pmon-name`	is the name of the PATHMON process associated with the error.
`server-class-name`	is the name of the Pathway server class that exceeded the PATHSEND retry count.

Cause The maximum number of PATHSEND retries for a Pathway server class request was reached.

Effect The activity stops in a restartable state.

Recovery The planner should examine the PATHSEND errors and other pertinent errors on the DSM/SCM log ($DISK.ZDSMSCM.ZZEVnnnn) or the EMS event log. The problem might be within DSM/SCM, or it might be a PATHMON configuration error.

2000

Error returned from SWID utility, p-error, s-error on filename. Correct the error and RESTART the activity.

`p-error`	is the P error value. For possible P error values that can be returned and brief descriptions of their meanings, see Table 27-1.
`s-error`	is the S error value. For possible S error values that can be returned and brief descriptions of their meanings, see Table 27-1.
`filename`	is the file name in the internal format of the file where the SWID error occurred.

Cause The Software File Identification (SWID) utility returned an error based on the values of P error and S error.

Effect The activity stops in a restartable state.

Recovery Correct the error and restart the activity according to the values of the P error and S error in Table 27-1. For more information on S errors, see the Guardian Native C Library Calls Reference Manual.

Table 27-1 SWID P Error and S Error Values and Their Text Messages

P error value	Text Message	S error values	Text Message
-2	NA (not available)	0
-1	Not Computed	0
0	(no error)	0
301	I/O error	-11 through -1	`errtext`, where `errtext` is the name for the serror() function of the Guardian C Library
	1 through 255	Guardian error `num`, where `num` is the value of the serror
	401	Unsupported object file format
	402	NA
	403	NA
302	Error in licensing file	1 through 255	Guardian error `num`, where `num` is the value of the serror

2005

File error file-error with description utility-error returned from utility utility-name, during action-name on file-type, filename. Correct error, if necessary, or Contact HP. RESTART activity.

file-error

is the file-system error that occurred. File-system errors are defined in the Guardian Procedure Errors and Messages Manual.

utility-error

is the error text from the utility server.

utility-name

is the name of the utility where the file-system error occurred. Possible values:

FILE MANAGER

TAPE READER

action-name

is the name of the procedure that was in progress when the file error occurred. Possible values:

READ

WRITE

WRITEREAD

file-type

is the file type of the file. Possible values:

Activation Package	SYSGEN Input Product File
Configuration Information File	SYSGEN Output File
System Snapshot	Target File
Software Input	Tool File

filename

is the file name in the internal format of the file where the error occurred.

Cause A file warning or error occurred at the File Manager or Tape Reader utility.

Effect If this is a file error, the error stops the activity in a restartable state. If this is a file warning, the activity continues processing.

Recovery Check the file-system error and text in the message. For more information, including recovery actions, see the Guardian Procedure Errors and Messages Manual. If necessary, correct the error and restart the activity.

2010

Error proc-name error-code returned from SWARC. SWARC failed to compress/decompress file. Contact HP.

`proc-name`	is the name of the procedure where the error occurred.
`error-code`	is the error code returned by the Software Archive (SWARC) utility. For SWARC error codes, see the Software Identification (SWID) User’s Guide.

Cause The SWARC utility could not compress or decompress a file.

Effect The activity stops in a nonrestartable state.

Recovery A problem occurred with DSM/SCM or the SWARC utility. Contact your service provider and provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated, including the procedure name and error code in the message
Supporting documentation such as the $ZPHI Event Management Service (EMS) logs and trace files (if requested by your service provider)

2015

Specified file-type file filename on medium has incorrect error-entity. Ensure filename is correct and created by DSM/SCM. Otherwise, save file, CANCEL activity. Contact your HP representative.

file-type

is the file type of the file where the error occurred. Possible values:

Activation Package

Archive File

System Snapshot

filename

is the file name in the internal format of the file where the error occurred.

medium

is the type of medium where the error occurred. Possible values:

disk

tape

error-entity

indicates the entity in the file where the inconsistency occurred. Possible values:

activity ID

header file type

header file code

header file size

host name

target name

Cause A file inconsistency existed in the activation package, system snapshot, or archive file located on the medium type specified. Either the file name specified was incorrect, or a data entity in the file was invalid.

Effect The activity stops in a restartable state.

Recovery The planner should check that the correct file name was specified and that the file itself was created by DSM/SCM and is the correct type. If you cannot detect the cause of the error, save the file, cancel this activity, contact your service provider, and provide all relevant information:

Descriptions of the problem and accompanying symptoms
A copy of the file that caused the error
Details from the message or messages generated
Supporting documentation such as the $ZPHI Event Management Service (EMS) logs and trace files (if requested by your service provider)

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.

2017

You specified a snapshot file filename created at a target target-name not managed by this host host-name. Ensure you have the correct medium for this host.

filename

is the file name in the internal format of the system snapshot file.

target-name

is the node name of the target contained in the snapshot file. This target is not managed by this host.

host-name

is the node name of this host.

medium

is the type of medium where the error occurred. Possible values:

disk

tape

Cause An incorrect system snapshot file was specified. The specified system snapshot file was for a target that this host does not manage.

Effect The activity stops in a restartable state.

Recovery Verify that you specified the correct tape or disk location. Correct the error. Restart the activity.

2020

Correctable database error db-error-num. SQL/data base manager returned db-error-buf. Correct error. RESTART activity.

`db-error-num`	is the SQL error code that identifies the error. For SQL error codes, see the SQL/MP Messages Manual. Some common values are described here.
`db-error-buf`	contains the structured query language communications area (SQLCA) error text passed from SQL/MP.

Cause A database error occurred that caused DSM/SCM to stop processing.

Effect The activity stops in a restartable state.

Recovery For exact determination of the correctable database error, see this list of error codes. Correct the error; then restart the activity. If you cannot correct the problem, save the file, cancel this activity, contact your service provider, and provide all relevant information:

Descriptions of the problem and accompanying symptoms
A copy of the file that caused the error
Details from the message or messages generated
Supporting documentation such as the $ZPHI Event Management Service (EMS) logs and trace files (if requested by your service provider)

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.

5	DB_ERR_IPC_FAILURE
	A failure occurred while DSM/SCM was trying to communicate with the database manager. The most common reason for this failure is that the define set up in the Pathway environment does not point to the correct database manager.
6	DB_ERR_SECURITY_VIOLATION
	The transaction does not have access to an object in the database.
7	DB_ERR_NOT_ENOUGH_MEMORY
	Not enough memory is available to complete the transaction.
17	DB_ERR_DEFINE_NOTFOUND
	The define pointing to the database manager does not exist.
23	DB_ERR_BEGIN_TRANSACTION_FAILED
	Cannot begin a transaction. Check the TMF status for errors.
38	DB_ERR_UNABLE_TO_RET_TARGETS_DEFINE
	The transaction tag passed to the database manager does not match the tag that corresponds to the transaction that this database manager process started.
-8300	SQL/MP encountered a file-system error. The file-system error and a one-line description are displayed as part of `db-error-buf`.If 0035 is the file-system error:Cannot obtain an I/O process control block, or the transaction or open lock unit has been reached. This can occur during the check-in stage of a software input or when a physical target is being deleted.The MAXLOCKSPERTCB value might have been exceeded. The default is 5000. To increase this parameter value, assigned to the disk that contains the database table in `db-error-buf`, on a NonStop K-series system: > STOPSCM > TMFCOM; STOP TMF > FUP LISTOPENS $disk.. > PUP LISTDEV $disk (Note the LDEV and UNIT numbers for later.) > PUP DOWN $disk > COUP 1) ASSUME DEVICE 2) INFO $ldev-num, DETAIL 3) SET LIKE $ldev-num 4) SHOW 5) STOP $ldev-num 6) DELETE $ldev-num 7) SET UNIT unit-num 8) SET MAXLOCKSPERTCB 6000 9) ADD $disk 10) START $disk 11) EXIT > TMFCOM; START TMF > STARTSCM > Restart the activity. On a NonStop S-series system, you do not need to stop TMF or the disk with the DSM/SCM database. Log on as the super ID and use SCF:> SCF ALTER DISK $DSMSCM,MAXLOCKSPERTCB 6000

2030

error-type file-error on action-name of file/process filename. If error type is Warning, decide upon corrective action. If error type is Restartable, correct error and RESTART activity.

error-type

indicates whether the error is restartable or a warning. Possible values:

Restartable error

Warning

file-error

is the file-system error that occurred. For file-system error definitions, see the Guardian Procedure Errors and Messages Manual.

action-name

is the name of the procedure or action during which the error occurred. Possible values:

AWAITIO	OPEN
CLOSE	POSITION
CONTROL	PUP Listlabel
CREATE	READ
DELETE	READUPDATE
DEVICEINFO2	RENAME
DISKINFO	REPLY
DSC SPI command CONFIG	Safeguard access check
DSC SPI command LISTDEV	Safeguard command ADD FILE
EDITREAD	Safeguard command DELETE FILE
FILEINQUIRE	SETMODE
FUP Dup	STOP
EDITREADINIT	TAPEMOUNT
FILEINFO	UNLOCK
NEWPROCESS	WRITE
NEXTFILENAME	WRITEREAD

filename

is the file name in the internal format of the file where the error occurred.

Cause A warning or restartable file error occurred during the specified procedure or action.

Effect If the error is a warning, the activity continues processing. If the error is restartable, the activity stops in a restartable state.

Recovery Check the file-system error code in the message. For more detailed information, including recovery actions, see the Guardian Procedure Errors and Messages Manual. If the error is a warning, the operator or planner might need to decide if corrective action is needed. If the error is restartable, correct the error and restart the activity.

If the filename was $EMSLOGF.ILEERROR, the server process could not send an EMS message out to the DSM/SCM EMS collector. Instead, this error was reported back to the Schedule Manager on behalf of the server that could not send out the message. This is most likely caused by an internal code error where an EMS message routine was not called. Performing a trace will help identify the faulty code to development.

2031

error-type file-error on action-name of process process-name, file filename. If error type is Warning, decide upon corrective action. If error type is Restartable, correct error and RESTART activity.

error-type

indicates whether the error is restartable or a warning. Possible values:

Restartable error

Warning

file-error

is the file-system error that occurred. For file-system error definitions, see the Guardian Procedure Errors and Messages Manual.

action-name

is the name of the procedure or action during which the error occurred. Possible values:

AWAITIO	OPEN
CLOSE	POSITION
CONTROL	PUP Listlabel
CREATE	READ
DELETE	READUPDATE
DEVICEINFO2	RENAME
DISKINFO	REPLY
DSC SPI command CONFIG	Safeguard access check
DSC SPI command LISTDEV	Safeguard command ADD FILE
EDITREAD	Safeguard command DELETE FILE
FILEINQUIRE	SETMODE
FUP Dup	STOP
EDITREADINIT	TAPEMOUNT
FILEINFO	UNLOCK
NEWPROCESS	WRITE
NEXTFILENAME	WRITEREAD

process-name

is the process name in the internal format of the process where the error occurred.

filename

is the program name in the internal format of the process where the error occurred.

Cause A warning or restartable file error occurred during the specified procedure or action.

Effect If the error is a warning, the activity continues processing. If the error is restartable, the activity stops in a restartable state.

Recovery Check the file-system error code in the message. For more information, including recovery actions, see the Guardian Procedure Errors and Messages Manual. If the error is a warning, the operator or planner might need to decide if corrective action is needed. If the error is restartable, correct the error and restart the activity.

2032

error-type file-error on procedure of OSS file pathname If error type is Warning, decide upon corrective action. If error type is Restartable, correct error and RESTART activity.

error-type

indicates whether the error is restartable or a warning. Possible values:

Restartable error

Warning

file-error

is the OSS file-system error that occurred. For OSS file-system error definitions, see the Open System Services System Calls Reference Manual.

procedure

is the procedure or action during which the error occurred. Possible values:

utime() procedure	fwrite() procedure
chmod() procedure	opendir() procedure
readlink() procedure	mkdir() procedure
stat() procedure	mkfifo() procedure
lstat() procedure	remove_oss() procedure
fseek() procedure	link() procedure
fopen_oss() procedure	symlink() procedure
fread() procedure

pathname

is the qualified filename of the file on which the error occurred.

Cause A warning or restartable error occurred during the specified procedure or action.

Effect For a warning, the activity continues processing. For a restartable error, the activity stops in a restartable state.

Recovery Check the OSS file-system error code in the message. For a definition of the specified error and recovery actions, see the Open System Services System Calls Reference Manual. If the error is a warning, the operator or planner might need to decide if corrective action is needed. If the error is restartable, correct the error and restart the activity.

2033

error-type file-error on action-name of file/process filename. If error type is Warning, decide upon corrective action. If error type is Restartable, correct error and RESTART activity.

error-type

indicates whether the error is restartable or a warning. Possible values:

Restartable error

Warning

file-error

is the file-system error that occurred. For file-system error definitions, see the Guardian Procedure Errors and Messages Manual.

action-name

is the name of the procedure or action during which the error occurred. Possible values:

AWAITIO	OPEN
CLOSE	POSITION
CONTROL	PUP Listlabel
CREATE	READ
DELETE	READUPDATE
DEVICEINFO2	RENAME
DISKINFO	REPLY
DSC SPI command CONFIG	Safeguard access check
DSC SPI command LISTDEV	Safeguard command ADD FILE
EDITREAD	Safeguard command DELETE FILE
FILEINQUIRE	SETMODE
FUP Dup	STOP
EDITREADINIT	TAPEMOUNT
FILEINFO	UNLOCK
NEWPROCESS	WRITE
NEXTFILENAME	WRITEREAD

filename

is the file name in the internal format of the file where the error occurred.

Cause A warning or restartable file error occurred during the specified procedure or action.

Effect If the error is a warning, the activity continues processing. If the error is restartable, the activity stops in a restartable state.

Recovery Check the file-system error code in the message. For a definition of the specified error, and more detailed information, including recovery actions, see the Guardian Procedure Errors and Messages Manual. If the error is a warning, the operator or planner might need to decide if corrective action is needed. If the error is restartable, correct the error and restart the activity.

If the file name was $EMSLOGF.ILEERROR, the server process could not send an EMS message out to the DSM/SCM EMS collector. Instead, this error was reported back to the Schedule Manager on behalf of the server that could not send out the message. Most likely an EMS message routine was not called because of an internal code error. Performing a trace will help identify the faulty code to development.

2034

error-type file-error on action-name of file/process filename. If error type is Warning, decide upon corrective action. If error type is Restartable, correct error and RESTART activity.

error-type

indicates whether the error is restartable or a warning. Possible values:

Restartable error

Warning

file-error

is the file-system error that occurred. For file-system error definitions, see the Guardian Procedure Errors and Messages Manual.

action-name

is the name of the procedure or action during which the error occurred. Possible values:

AWAITIO	OPEN
CLOSE	POSITION
CONTROL	PUP Listlabel
CREATE	READ
DELETE	READUPDATE
DEVICEINFO2	RENAME
DISKINFO	REPLY
DSC SPI command CONFIG	Safeguard access check
DSC SPI command LISTDEV	Safeguard command ADD FILE
EDITREAD	Safeguard command DELETE FILE
FILEINQUIRE	SETMODE
FUP Dup	STOP
EDITREADINIT	TAPEMOUNT
FILEINFO	UNLOCK
NEWPROCESS	WRITE
NEXTFILENAME	WRITEREAD

filename

is the file name in the internal format of the file where the error occurred.

Cause A warning or restartable file error occurred during the specified procedure or action.

Effect If the error is a warning, the activity continues processing. If the error is restartable, the activity stops in a restartable state.

If the file name was $EMSLOGF.ILEERROR, the server process could not send an EMS message out to the DSM/SCM EMS collector. Instead, this error was reported back to the Schedule Manager on behalf of the server that could not send out the message. Most likely an EMS message routine was not called because of an internal code error. Performing a trace will help identify the faulty code to development.

2035

Remote system remote-node-num not available. RESTART the activity when the remote system is available.

remote-node-num

is the name of the remote system that was not available.

Cause A user request to a remote system could not be finished because the remote system was not available.

Effect The activity stops in a restartable state.

Recovery Determine why the Expand line is down or unavailable. If possible, correct the problem that is causing the line to be down. Restart the activity when the remote system is available.

2040

Memory allocation error. RESTART the activity. If the error persists, contact your HP representative.

Cause A memory allocation error occurred.

Effect The activity stops in a restartable state.

Recovery Restart the activity. If the error persists, contact your service provider and provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as the $ZPHI Event Management Service (EMS) logs and trace files (if requested by your service provider)

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.

2045

server-process completed server-completion-code. Examine server warning(s)/error(s), correct error(s) if necessary, RESTART activity if stopped in a restartable state.

server-process

is the server process that has completed the activity. Possible values:

BACKUP	TACL
SQLCI	TFORM
SYSGEN	TGAL
SYSGENR

server-completion-code

is the server completion status of the activity. Possible values and the status they represent are:

Value	Description
with error(s)	Activity completed with errors.
successfully	Activity completed successfully.
with warning(s)	Activity completed with warnings.

Cause A server process has completed an activity for DSM/SCM. The activity has completed successfully, with warnings, or with errors.

Effect Depending on the completion status, either the server completed processing the activity (if the server completes successfully or with warnings), or the server process stopped processing the activity (if the server stops with errors). If the server process stops with errors, the activity stops in a restartable state.

Recovery The recovery procedure depends on the returned value of the server completion code:

If the server process completes the activity successfully, this is an informational message only. No corrective action is needed.
If the server process completes the activity with warnings, the operator should examine the messages from the server process and any appropriate output files to determine if corrective action is needed. (SYSGEN/R always finishes with warnings.) If corrective action is needed, correct the error and start a new activity.
If the server process completes the activity with errors, the operator should examine the messages from the server process and any appropriate output files to determine the corrective action needed. Correct the error, then either cancel the activity and resubmit it after the corrections have been made, or restart the activity.

2046

server-process completed server-completion-code. Completion text: server-completion-text. Examine server warning(s)/error(s) in filename, correct error(s) if necessary, RESTART activity if stopped in a restartable state.

server-process

is the server process that has completed the activity. Possible values:

BACKUP	TACL
SQLCI	TFORM
SYSGEN	TGAL
SYSGENR

server-completion-code

is the server completion status of the activity. Possible values and the status they represent are:

Value	Description
with error(s)	Activity completed with errors.
successfully	Activity completed successfully.
with warning(s)	Activity completed with warnings.

server-completion-text

is the text in the termination message from the server process. The text contains information about the errors or warnings. Some servers do not return any text.

filename

is the file name of the output file for the server process. This file might contain more information about the errors or warnings.

Cause A server process completed an activity for DSM/SCM. The activity completed successfully, with warnings, or with errors.

Effect Depending on the completion status, the server process completed processing the activity (if it completes successfully or with warnings), or the server stopped processing the activity (if it stops with errors). If the server process stops with errors, the activity stops in a restartable state.

Recovery Recovery depends on the returned value of the server completion code:

If the server process completes the activity successfully, this is an informational message only; no corrective action is needed.
If the server process completes the activity with warnings, examine the messages from the server process and any appropriate output files to determine if corrective action is needed. If corrective action is needed, correct the error and start a new activity.
If the server process completes the activity with errors, examine the messages from the server process and any appropriate output files to determine the corrective action needed. Correct the error. Then either cancel the activity and resubmit it after the corrections have been made, or restart the activity.

2047

server-process completed successfully. See the output at the server-process-output.

server-process

is the server process that completed the activity successfully. Possible values:

Sysgen (OSBUILD)

Public DLL Build (PLINSTL)

server-process-output

is the server output location; for example:

\NODE.$S.#SYSGEN.

Cause A server process has completed an activity successfully for DSM/SCM.

Effect The activity continues.

Recovery Informational message only; no corrective action is needed.

2048

server-process completed server-completion-code. Completion text: server-completion-text. Examine server warning(s)/error(s) in file server-process-output or for TACL errors in filename. Correct error(s) if necessary, RESTART activity if stopped in a restartable state.

Cause The OS Builder server process has completed with errors.

Effect The build stops in restartable stage.

Recovery The operator has to examine the messages from the server process and any appropriate output files to determine the corrective action needed. Correct the error and then restart the activity.

2050

PATHSEND link down, processing terminated. Correct any associated error(s). RESTART the activity.

Cause A PATHSEND link that DSM/SCM uses was down.

Effect The activity stops in a restartable state.

Recovery Determine why the link is down or unavailable, correct any associated errors, and restart the activity when the link is available. For Pathsend error definitions, see the TS/MP Pathsend and Server Programming Manual.

2055

Cannot create unique name for file-type file on subvolume-name. Delete unneeded files. RESTART activity.

file-type

is the file type of the affected file. Possible values:

Activation Package

System Snapshot

Archive File

Trace

subvolume-name

is the subvolume name where the problem occurred.

Cause DSM/SCM could not create a unique name for a file because of a problem with the cleanup of a previous DSM/SCM activity.

Effect The activity stops in a restartable state. Work files remain at the location specified.

Recovery Clean up unneeded files at the subvolume specified, or specify a new volume for the scratch or archive volume in the Maintenance Interface. Restart the activity.

2057

Cannot create unique name for file-type file in directory TDL-name. Delete unneeded files. RESTART activity.

`file-type`	is the file type of the affected file. For this event message, the value is always OSS map file.
`TDL-name`	is the target directory location name where the problem occurred.

Cause DSM/SCM could not create a unique name for a file because of a problem with the cleanup of a previous DSM/SCM activity. The needed filename is .dsmscm.ZMPccncc, where c is any uppercase alphanumeric character and n is any digit. If this error occurs, there are over 16 million files in the directory.

Effect The activity stops in a restartable state. Work files remain at the specified location.

Recovery Clean up unneeded files at the specified subvolume, then restart the activity.

2060

Invalid token value returned from EMS, token-name, ems-error.

`token-name`	is the name of the token that EMS does not recognize.
`ems-error`	is the error code that EMS returns. For EMS error codes, see the EMS Manual.

Cause EMS does not recognize the requested token.

Effect The unrecognized token is reported in this message. The activity continues processing.

Recovery Informational message only; no corrective action is needed.

2065

Existence check on file-type file filename received error file-error.

file-type

is the file type of the file that could not be found. Typical returned values are:

Activation Package	     Target File
System Snapshot	     Tool File
SYSGEN Input Product File

For a complete list of the possible file-type values, see the description of message 5095.

filename

is the file name in the internal format of the file that could not be found.

file-error

is the file-system error that occurred. (The cause for error 179 is described here.)

Cause DSM/SCM could not locate the specified file. Possible causes of this error are:

The file name was mistyped through the Planner Interface or Target Interface.
The file was moved, renamed, modified, or deleted.
If file-system error 179 (FEBADFORMAT) was returned, the file existed, but one or more of its attributes (either the fingerprint, end-of-file, or modification timestamp) did not match those in the database.

Effect The activity stops in a restartable state.

If the error occurred because the intended file is not in the proper location, put the file in the appropriate location, and restart the activity.
If the error occurred because the file was incorrectly specified, cancel the activity and start a new activity.

2066

Existence check on file-type OSS file filename received error file-error. Ensure filename is correct and file has not been removed, renamed, or deleted.

`file-type`	is the file type of the file that could not be found. For this event message, the type is always OSS target file.
`filename`	is the file name in the internal format of the OSS file that is missing or has an unexpected last modification time.
`file-error`	is the OSS file-system error that occurred. For file-system error definitions, see the Open System Services System Calls Reference Manual.

Cause The specified OSS file was changed or removed during an Apply. The Apply already checked which files in the configuration are missing or changed, and the necessary files were placed. The specified file was changed or removed after the Apply checked to see which files to place.

Effect The activity stops in a restartable state. Work files remain at the specified location.

Recovery Restart the Apply. The Apply again rechecks which files to place, discovering the specified file as missing or changed, and places a new file.

2070

Server class parameter missing or invalid: parameter parameter-name, value parameter-value. Planner must correct Pathway configuration to correct parameter.

`parameter-name`	is the name of the server class parameter that is missing or invalid.
`parameter-value`	is the value of the server class parameter that is invalid. If the server class parameter is missing, the value of this parameter is null.

Cause A server class parameter in the DSM/SCM PATHMON configuration file was missing or had an invalid value.

Effect The activity stops in a restartable state.

Recovery The planner must correct the PATHMON configuration file to either include the parameter specified or assign the parameter its correct value. Restart the activity.

2075

file-type file filename on medium contains invalid data. Correct the error and RESTART the activity.

file-type

is the file type of the file. Possible values:

Activation Package

System Snapshot

Target File

filename

is the filename in the internal format of the file.

medium

is the type of medium where the error occurred. Possible values:

disk

tape

Cause The specified file contains invalid data. Either the specified file name is incorrect, or the file is corrupted and does not contain the data expected to be there.

Effect DSM/SCM cannot process the activity because the specified file or data in the file is not available.

Recovery If the file name is incorrect, restart the activity with the correct file name. If the file is corrupted, re-create the file using the appropriate measures:

If the file is a system snapshot, request a new independent snapshot at the target.
If the file is an activation package, request a new Build of the software revision.
If the file is a target file, request a new independent snapshot of the target and then request a new Build of the software revision.

2080

Error file-error renaming file from current-filename to proposed-filename. Contact security administrator or Planner if problem is a security or user error.

`file-error`	is the file-system error that is returned. For file-system error definitions, see the Guardian Procedure Errors and Messages Manual.
`current-filename`	is the current file name in the internal format of the file.
`proposed-filename`	is the proposed new file name in the internal format of the file.

Cause An internal error occurred in renaming a file, or a security problem occurred with the file rename.

Effect The activity stops in a restartable state.

Recovery Check the file-system error code in the message. For more information, including recovery actions, see the Guardian Procedure Errors and Messages Manual. If the error resulted from a security problem at your site, the security administrator should correct the problem. If the error resulted from a user purging the file, contact the planner.

2081

Error file-error renaming OSS file current-filename to proposed-filename. Contact security administrator or Planner if the problem is a security or user error.

`file-error`	is the OSS error that is returned. For OSS error definitions, see the Open System Services System Calls Reference Manual.
`current-filename`	is the current filename in the internal format of the file.
`proposed-filename`	is the proposed new filename in the internal format of the file.

Cause An internal error occurred in renaming an OSS file, or a security problem occurred with the file rename.

Effect The activity stops in a restartable state.

Recovery Check the OSS error code in the message. For a definition of the specified error, see the Open System Services System Calls Reference Manual. If the error resulted from a security problem at your site, the security administrator should correct the problem. If the error resulted from a user purging the file, contact the planner.

2085

filename is incorrectly specified. RESTART activity specifying the correctly formatted name.

filename

is the filename of the file that is incorrectly specified.

Cause The specified file could not be converted to an internal filename format. The filename was probably entered incorrectly.

Effect The activity stops in a restartable state.

Recovery If you can bring up the system where the file is located, restart the activity, specifying a correct filename of the form \node.volume.subvolume.filename. If you cannot bring up the system where the file is located, cancel the activity.

2090

Insufficient disk space on volume-type volume(s) or no volume-type volumes specified. Use DSM/SCM Maintenance Interface to indicate usable volume-type volumes.

volume-type

indicates whether the volume is an archive or scratch volume. Possible values:

ARCHIVE

SCRATCH

Cause The space requirements for the activity exceeded the space remaining on volumes in the list of archive or scratch subvolumes, or no archive or scratch volumes were specified.

Effect The activity stops in a restartable state.

Recovery The site database administrator should reconstruct the target archive or scratch volume list through the Maintenance Interface to include usable volumes.

2095

Pathway configuration error. Server class server-class-name, PATHMON pmon-name must run on host-name node.

`server-class-name`	is the name of the Pathway server class that is running on an incorrect node.
`pmon-name`	is the name of the PATHMON process associated with the Pathway server class.
`host-name`	is the host name of the node where the Pathway server class should be running.

Cause A Pathway server class was running on the incorrect node. It should be running on the node specified.

Effect The activity stops in a restartable state.

Recovery The operator should reconfigure the Pathway server class to execute on the correct target node and restart the activity.

2100

DSM/SCM exceeded an internal threshold while trying to create a unique name for file-type file on subvolume-name. Delete unneeded files from subvolume.

file-type

is the type of file that could not be created. Possible values:

Activation Package

System Snapshot

Trace

subvolume-name

is the name of the subvolume where the error occurred.

Cause DSM/SCM could not create a unique name for a file because the subvolume or reserved subvolume already contained another file with the same name.

Effect The activity stops in a restartable state.

Recovery Delete any unneeded files on the subvolume specified.

2101

An empty public-dll-subvolume[A-Z] subvolume could not be found to place public DLLs in. Remove or rename one or more of these subvolumes and restart the Apply.

public-dll-subvolume

is the fully qualified subvolume name that DSM/SCM uses to create a new target subvolume (TSV) for public DLLs.

Cause An empty ZDLLrrr[a] subvolume to place public DLLs in could not be found. All 27 possible subvolumes already exist.

Effect The Apply stops restartable.

Recovery Remove or rename one or more of these subvolumes that are no longer needed and restart the Apply. DSM/SCM no longer needs these subvolumes if there is no ZPHI6030 file present.

2105

DSM/SCM cannot process the same conflict-file-type file for two different conflict-op-type at the same time. Retry the request request-name later.

conflict-file-type

is the type of file where the conflict occurred. Possible values:

software input

sysgen output

conflict-op-type

is the type of operation that was in progress when the conflict occurred. Possible values:

software inputs

sysgen outputs

request-name

is the name of the request that generated the error.

Cause A database input conflict occurred when DSM/SCM attempted to process the same file for two different activities at the same time.

Effect The activity stops in a restartable state.

Recovery Retry your activity later when conflicting active requests have completed execution.

2110

filename needs to be licensed before activity can proceed. RESTART the activity after the file has been licensed.

filename

is the file name in the internal format of the file that is not licensed.

Cause The activity could not proceed because it required the use of a program file that was not licensed.

Effect The activity stops in a restartable state.

Recovery License the file and restart the activity.

2115

Invalid username user-name.

user-name

is the user name that is invalid.

Cause The specified user name was invalid.

Effect The activity stops in a restartable state.

Recovery Correct the user name. Cancel and resubmit the activity with a valid user name.

2120

Invalid userid user-ID.

user-ID

is the invalid user-ID (the group-ID and member-ID together). For example:

user-ID	group-ID	member-ID
00	0	0
999	9 or 99	99 or 9
9999	99	99 (not 999 because > 255)
2255	2 or 22 or 225	255 or 55 or 5
2030	20	30 (not 2030 because no leading zero)

Cause The specified user-ID is assigned to a file but does not have a defined group-name member-name. Running USERS group-ID,member-ID will return "NO SUCH USERS WERE FOUND." for this user-ID. This is usually caused by a file being copied to a system from another system

Effect The activity stops in a restartable state.

Recovery Find the files that are owned by this user-ID with the FUP INFO $*.*.*,OWNER user-ID command. Either change the owner of these files or define the user-ID with the ADDUSER command. Restart the activity.

2125

Cannot proceed with activity. Necessary db-object-type db-object-name currently in use. Try request later.

db-object-type

is the type of database object in use. Possible values:

CONFIGURATION-MANAGER-PROFILE

CONFIGURATION-REVISION

SOFTWARE-INPUT

SYSTEM-PROFILE

db-object-name

is the name of the database object in use.

Cause The activity required a database object that another activity was using.

Effect The activity stops in a restartable state.

Recovery Retry your activity later when active requests have completed execution.

2130

A necessary database object is in use by another request request-name. Restart this request after request-name has completed.

request-name

is the name of the request that is already using the database object.

Cause Another request was running and locked the database object that this activity needed. This activity cannot proceed until the database object is freed.

Effect The activity stops in a restartable state.

Recovery Retry the activity later after the specified request has completed execution.

2140

file-type file filename on media-type has incorrect version. Expected version: version-1 or lower. Actual version: version-2. Current internal DSM/SCM version: version-3. This file was created by a later version of DSM/SCM who believes our Internal DSM/SCM version is later than indicated. CANCEL Apply, Perform an Independent Snapshot, and repeat the Build/Apply.

`file-type`	is the type of file—always an activation package file for this message.
`filename`	is the name in internal format of the activation package file where the error occurred.
`media-type`	is the type of media on which the error occurred (disk or tape).
`version-1`	is the expected version of the file. This is the highest version of the file that can be processed.
`version-2`	is the actual version of the activation package file.
`version-3`	is the internal DSM/SCM version that sent this message. This is the version number sent between DSM/SCM systems to determine the appropriate versions of files to use when sending information.

Cause The specified activation package file was created by a host system running a different DSM/SCM PVU than the target it is intended for. The host database indicated that the DSM/SCM PVU on the target system was later than it actually is, so a later version of the specified file was created, which the target cannot understand. This error might occur if the DSM/SCM PVU on the target is lowered, and the host database is not updated before this Build/Apply. (To avoid this, when you lower the DSM/SCM PVU on a target, take an independent snapshot immediately to update the host database.)

If you are trying to use DSM/SCM to manage OSS files, the Manage OSS Files check box was selected for this target, but the target is running a DSM/SCM PVU that cannot install or manage OSS files.

Effect The request stops in a restartable state. A version of ZPHIUTL might be available to downgrade these activation package files to an appropriate version that this target system can read.

Recovery Check if the ZPHIUTL program on the host system can convert the activation package file to a lower version, using the CONVERT command. If so, convert the file to a lower version and restart the activity. If not, cancel the Apply, take an independent snapshot, and repeat the Build/Apply.

If the activation package contains OSS products and that target is running a pre-D46 PVU of DSM/SCM, cancel the Apply and either clear the Manage OSS Files checkbox for this target or upgrade the target to the D46 or later DSM/SCM PVU.

2150

file-type file filename on media-type has incorrect version. Expected version: version-1 or lower. Actual version: version-2. Current internal DSM/SCM version: version-3. This file was created by a later version of DSM/SCM who believes our internal DSM/SCM version is later than indicated. CANCEL Snapshot, Perform another Build/Apply (specifying All Files if necessary).

`file-type`	is the type of file—always a snapshot file for this message.
`filename`	is the name of a snapshot file.
`media-type`	is the type of media on which the snapshot is transferred.
`version-1`	is the highest version of this file that can be interpreted by this host system.
`version-2`	is the actual version of the snapshot file.
`version-3`	is the internal DSM/SCM version of this host system.

Cause The specified snapshot file was created by a target system running a different DSM/SCM version than the host system. The target database indicated that the DSM/SCM version on the host system was later than it actually is, so a later version of the specified file was created, which the host cannot understand. This error might occur if the DSM/SCM version on the host is lowered, and the target database is not updated before this Build/Apply. (To avoid this, when you lower the DSM/SCM PVU on a host, perform a Build/Apply immediately to update the target database before the next snapshot is requested.)

Effect The request stops in a restartable state.

Recovery You have two options:

Upgrade the host to the version of the target, then restart the receive snapshot request.
On the target system, try to use the ZPHIUTIL CONVERT command to convert the snapshot file to a lower version. If this works, convert the file and restart the activity. If it does not work, cancel the snapshot and perform a Build/Apply to the target (specifying all files if necessary). This removes OSS management from the target, if it was present. The new snapshot is the old version.

2161

DSM/SCM requires version server-program-version or later of server file-name. The current server appears to be an earlier version. Manually put a new version of the server in place, and restart the activity.

server-program-version

indicates the minimum required PVU of SWID; for example, T9298AAJ.

file-name

is the fully qualified external server program file name. For example:

\NODE.$SYSTEM.SYSTEM.SWID

Cause This DSM/SCM PVU requires a newer PVU for a server program, such as SWID.

Effect The activity stops in a restartable state.

Recovery If you cannot install the server program, manually install a newer product version:

Copy the newer version of the server program to where the current product version is located and restart the activity.
Install this new product version of the server program with DSM/SCM.

2162

WARNING: Master target target-name_logical-target-name has no clone targets defined.

`target-name`	is the system name of the target defined as a master.
`logical-target-name`	is the logical target name of the target system defined as a master.

Cause No targets defined in DSM/SCM have the text “CLONE \system” in their target description text, point to this master target, and have the same target name as the Master (for example, DEFAULT).

Effect The activity continues and completes with warnings.

Recovery Remove the text “<MASTER>” from the target description text of the specified target, or define other targets to be a clone of this master target.

2163

WARNING: Clone target target-name_logical-target-name specifies undefined system name as its master: clone-text.

`target-number`	is the system name of the target defined as a clone.
`logical-target-name`	is the logical target name of the target system defined as a clone.
`clone-text`	is either the valid system name specified as the master or a portion of the logical target description text and error text describing the problem.

Cause The target description text for this target contains “CLONE \system”, and \system is not a defined system in DSM/SCM. The format of the target description text might be invalid.

Effect The activity continues and completes with warnings.

Recovery Remove the text “CLONE \system” from the target description text of the specified target, or specify a master target that is defined in DSM/SCM.

2164

WARNING: Clone target target-name_logical-target-name specifies master master-name that does not have a target by this name.

`target-name`	is the system name of the target defined as a clone.
`logical-target-name`	is the logical target name of the target system defined as a clone.
`master-name`	is the system name of the master target.

Cause The target description text for this target contains “CLONE \system”. \system is defined in DSM/SCM but not with a matching logical target name (for example, DEFAULT).

Effect The activity continues and completes with warnings.

Recovery Remove the text “CLONE \system” from the target description text of the specified target, or specify a master target that is defined in DSM/SCM.

2165

WARNING: Clone target target-name_logical-target-name specifies Master master-name which is not defined as a master.

`target-name`	is the system name of the target defined as a clone.
`logical-target-name`	is the logical target name of the target system defined as a clone.
`master-name`	is the system name of the master target.

Cause The target description text for this target contains “CLONE \system”. \system is defined in DSM/SCM with a matching target name but does not contain “<MASTER>” in its target description.

Effect The activity continues and completes with warnings.

Recovery Make the specified target a master, or specify a correct master target in the target description text for the clone.

2166

WARNING: Clone group targets have different CPU types: target-name_logical-target-master is master-cpu-type, host-name_logical-target-clone is clone-cpu-type.

`target-name`	is the system name of the target defined as a master.
`logical-target-master`	is the logical target name of the target system defined as a master.
`master-cpu-type`	is the processor type of the master.
`host-name`	is the system name of the clone target in the same clone group.
`logical-target-clone`	is the logical target name of the clone target in the same clone group.
`clone-cpu-type`	is the processor type of the clone target in the same clone group.

Cause Two members of a clone group have different processor types defined.

Effect The activity continues and completes with warnings.

Recovery Ensure that all targets in the clone group have the same processor type specified in their system profiles.

2997

Internal error error-num, error-buf.

`error-num`	is the internal error code that identifies the error. For possible values and brief descriptions of their meanings, see Table 27-2.
`error-buf`	is a buffer containing additional information associated with the error. The contents of this buffer vary based on `error-num`. For a brief description of the contents of this token, see Table 27-2.

Cause A DSM/SCM component issued an internal error.

Effect The activity stops in a nonrestartable state. DSM/SCM cannot process another activity until the planner or operator uses the Maintenance Interface to correct the problem.

Recovery Contact your HP support representative and provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as the $ZPHI Event Management Service (EMS) logs and trace files (if requested by your service provider)

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. If the error resulted in a security problem at your site, the security administrator should correct the problem. If the error resulted from a user purging the file, contact the planner.

2998

Fatal data base error db-error-num. SQL/data base manager returned db-error-buf. Contact your HP representative.

`db-error-num`	is the SQL error code that occurred. For SQL error code descriptions (indicated by a negative number or 100), see the SQL/MP Messages Manual.
`db-error-buf`	contains the structured query language communication area (SQLCA) error text passed from SQL/MP.

Cause An SQL error occurred that caused DSM/SCM to stop processing.

Effect The SQLCA error text is passed from SQL/MP. The activity stops in a nonrestartable state. DSM/SCM stops processing. You must use the Maintenance Interface to clean up the activity before DSM/SCM can process another activity.

Recovery For exact determination of the fatal database error, see the error codes here or the SQL error. For SQL error code descriptions, see the TS/MP Pathsend and Server Programming Manual. If necessary, contact your service provider and provide:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as the $ZPHI Event Management Service (EMS) logs and trace files (if requested by your service provider)

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.

1	DB_ERR_UNABLE_TO_RETRIEVE
	Cannot access a record from the database. The associated SQL error text describes the error in detail.
2	DB_ERR_UNABLE_TO_UPDATE
	Cannot modify a database record.
3	DB_ERR_UNABLE_TO_DELETE
	Cannot delete a database record.
4	DB_ERR_UNABLE_TO_ADD
	Cannot add a record to the database.
8	DB_ERR_LIST_NOT_IN_SYNC
	The database manager received an incorrect number of elements in the request buffer.
11	DB_ERR_NOT_FOUND
	The object does not exist in the database.
13	DB_ERR_INCORRECT_ACTION_CODE
	The action code for the transaction is incorrect.
14	DB_ERR_ALREADY_CHECKED_OUT
	The object has already been checked out by the user.
15	DB_ERR_ALREADY_EXISTS
	The object already exists in the database.
16	DB_ERR_CHECKED_OUT_BY_DIFF_USER
	The object has already been checked out by a different user.
18	DB_ERR_INIT_FAILURE
	An error occurred while the database manager was performing its initialization steps.
19	DB_ERR_DIFFERENT_USER
	The user ID of the requester is not what the database manager expects it to be.
20	DB_ERR_VERSION_MISMATCH
	This version of the database manager is different from the version the requestor is looking for.
21	DB_ERR_UNSOLICITED_MESSAGE
	The database manager received a message from an unknown process.
23	DB_ERR_BEGIN_TRANSACTION_FAILED
	A system error occurred.
24	DB_ERR_UNABLE_TO_BUILD_RESPONSE
	The number of records retrieved from the database for an activity is greater than allowed in an activity suite.
27	DB_ERR_INVALID_HOST_TARGET_FLAG
	The host-target-flag value is not H or T.
28	DB_ERR_INVALID_TRANSACTION_TAG
	The transaction tag passed to the database manager is invalid.
29	DB_ERR_RESUME_TRANSACTION_FAILED
	An error occurred while a resume transaction was being performed.
30	DB_ERR_END_TRANSACTION_FAILED
	The End TMF Transaction Operation (commit) resulted in an error.
31	DB_ERR_UNABLE_TO_OPEN_CURSOR
	An error occurred while DSM/SCM was trying to open an SQL cursor.
32	DB_ERR_GET_TRANSID_FAILED
	An error occurred while DSM/SCM was trying to obtain a TMF transaction ID.
33	DB_ERR_SUSPEND_TRANSACTION_FAILED
	An error occurred while DSM/SCM was performing a suspend transaction.
34	DB_ERR_TOO_MANY_RECORDS
	The number of records that the database manager returned is greater than the number of records that the response buffer can accommodate.
35	DB_ERR_INVALID_QUERY_CODE
	The query code is not within the range of expected values.
36	DB_ERR_DELPHI_SYSTEM_ERROR
	A DSM/SCM internal system error occurred.
37	DB_ERR_INVALID_NO_OF_RECORDS
	The number of records that the requestor sent does not match the number of records it intended to send.
39	DB_ERR_TRANSACTION_NOT_STARTED_BY_SELF
	The transaction tag passed to the database manager does not match the transaction tag that corresponds to the transaction that this database manager process started.
40	DB_ERR_INVALID_FUNCTION_CODE
	An invalid function code was passed to the database manager.
42	DB_ERR_NOT_RESERVED
	The database object is not reserved.
43	DB_ERR_RESERVED
	The object being accessed has been reserved by another activity.
47	DB_ERR_INVALID_OPTION_SPECIFIED
	The option specified to the database manager is invalid.
49	DB_ERR_UNKNOWN_COMMAND
	The command code specified to the database manager is not known.
52	DB_ERR_UNKNOWN_USG_STATE
	An internal error occurred. Most likely the database has been corrupted.
55	DB_ERR_INVALID_LCS
	This internal error indicates an invalid life-cycle state.
56	DB_ERR_CKOUT_NO_CKR
	The variant is checked out, but there is no associated checker variant.
58	DB_ERR_NOT_CHECKED_OUT
	The object has not been checked out.
62	DB_ERR_WRONG_USAGE_STATE
	An internal error occurred. Most likely the database has been corrupted.
66	DB_ERR_DIFFERENT_NODE
	In the list of files passed by the inventory collector, one of the files has a different node name than the others.
67	DB_ERR_DIFFERENT_VOL
	In the list of files passed by the inventory collector, one of the files has a different volume name than the others.
68	DB_ERR_DIFFERENT_SUBVOL
	In the list of files passed by the inventory collector, one of the files has a different subvolume name than the others.
69	DB_ERR_INVALID_LOC_TYPE_CODE
	An internal error occurred. An invalid location type code was specified while searching for activity records in the database.
70	DB_ERR_INVALID_TAPE_PURPOSE_CODE
	An internal error occurred. An invalid tape purpose code was specified while searching for activity records in the database.
71	DB_ERR_REV_NONEXISTENT
	The revision of the object does not exist.
72	DB_ERR_TOO_MANY_TSVS
	The number of target subvolumes is greater than a limit that the database manager set.
73	DB_ERR_SAME_PVL_DIFFERENT_DSVS
	The product version list has both CISC and RISC distribution subvolumes.
74	DB_ERR_INVALID_DSV_TYPE
	The DSV type specified is not CISC or RISC.
75	DB_ERR_INVALID_RELEASE_VERSION
	The RVU is neither C nor D.
76	DB_ERR_UNABLE_TO_LOCK
	Cannot lock the database table.

2999

Internal error internal-error, internal-error-buf.

`internal-error`	is the internal error code that identifies the error. For possible values and brief descriptions of their meanings, see Table 27-2.
`internal-error-buf`	is a buffer containing additional information associated with the error. The contents of this buffer vary based on the value of `internal-error`. For a brief description of the contents of this parameter, see Table 27-2.

Cause A DSM/SCM component issued an internal error.

Effect The activity stops in a nonrestartable state. The planner or operator must correct the problem using the Maintenance Interface before DSM/SCM can process another activity.

Recovery Contact your service provider and provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as the $ZPHI Event Management Service (EMS) logs and trace files (if requested by your service provider)

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.




	NOTE: These codes apply only to internal errors that EMS reports. If you encounter an internal error while using the Target Interface or Maintenance Interface, see the DSM/SCM Messages Manual.

Table 27-2 DSM/SCM Internal Error Codes in EMS Messages

DSM/SCM Error Code	Meaning	Buffer Contents
91	Secondary Server - Version mismatch between requester and server
92	Secondary Server - Invalid message code
93	Secondary Server - Out of memory
94	Secondary Server - DEVICE_GETINFOBYLDEV_error
95	Secondary Server - DSC_DISK_GET_LABELS_ error
200	Invalid activity code	Tag, activity code
201	Inconsistent data	Tag, entities [SS, AP, IPC]
202	Invalid Pathway server class parameter	Tag, parameter name, value
203	Invalid information received from database	Tag, token name, value
204	Invalid internal parameter	Tag, parameter name, value
205	Invalid return value	Tag, parameter name, value
206	Invalid IPC parameter	Tag, parameter name, value
207	Incompatible data between IPC and database	Tag, parameter name, IPC value, db value
208	Error returned from Guardian procedure	Tag, procedure name, return value
209	Version incompatibility	Entity received version #, expected version #
210	Cannot access device
400	No available subvolume	Volume, subvolume prefix
401	Tool not found	Tool name, PVL release version
500	No available SS filename	Volume, subvolume prefix
502	No file instruction available for AP data file	File name, media
600	User function does not match activity records
601	Cannot initialize request, target not specified
602	Cannot add activity record, wrong status	Parameter = status
603	Cannot schedule activity record	Parameter = status
604	Activity records for request missing

3000

Specified snapshot file is not most recent for target-name. Not processed.

target-name

is the node name of the target that received the outdated file.

Cause An outdated system snapshot file was received at a host.

Effect The specified system snapshot file is not processed.

Recovery Informational message only; no corrective action is needed.

3005

The DSV subvolume-name does not contain A0CINFO file. Planner must use NonStop Software Essentials Package Software to create a correct A0CINFO file, bring it in as a separate input and assign to same input group through NonStop Software Essentials Package Software. DSV skipped, processing continues.

subvolume-name

is the name of the distribution subvolume (DSV) where the error occurred.

Cause The specified DSV did not contain an A0CINFO file.

Effect The activity finishes with warnings. The DSV is not processed as part of the current input.

Recovery The planner should use NonStop Software Essentials Package Software to create an A0CINFO file for the DSV. If you need help completing the correct NonStop Software Essentials Package Software processing, contact the product vendor. Because the DSV has been skipped, you must bring the DSV into DSM/SCM as a separate input. You can then assign both inputs to the same input group through NonStop Software Essentials. If the input is a release version update (RVU) or a software product revision (SPR), contact your service provider and provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as the $ZPHI EMS logs and trace files (if requested by your service provider)

If your local operating procedures require contacting the Global Customer Support Center (GCSC), supply your system number and the numbers and versions of all related products as well.

3006

The DSV subvolume-name does not contain A1CINFO file. DSV skipped, processing continues.

subvolume-name

is the name of the distribution subvolume (DSV) where the error occurred.

Cause The specified DSV did not contain an A1CINFO file, or the A1CINFO file has an incorrect file code.

Effect The activity finishes with warnings. The DSV is not processed as part of the current input.

Recovery A new DSV must be generated. Contact the product vendor. Because the DSV was skipped, you must bring the DSV into DSM/SCM as a separate input. You can then assign both inputs to the same input group through the Planner Interface. If the input is a release version update (RVU) or a software product revision (SPR), contact your service provider and provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details from any generated messages
Supporting documentation such as the $ZPHI EMS logs and trace files (if requested by your service provider)

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.

3007

The DSV subvolume-name has an entry in the A0CINFO file for A7CINFO file, which is not present in the DSV. DSV skipped, processing continues.

subvolume-name

is the name of the distribution subvolume (DSV) where the error occurred.

Cause The A7CINFO file was removed from the DSV after the A0CINFO file was generated.

Effect The activity finishes with warnings. The DSV is not processed as part of the current input.

Recovery A new DSV must be generated. Contact the product vendor. Because the DSV is skipped, you must bring the DSV into DSM/SCM as a separate input. You can then assign both inputs to the same input group through the Planner Interface. If the input is a release version update (RVU) or a software product revision (SPR), contact your service provider and provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details from any generated messages
Supporting documentation such as the $ZPHI EMS logs and trace files (if requested by your service provider)

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.

3008

pax archive file pax-filename in DSV DSV-name contains invalid file filename. File in /G or /E are not allowed. DSV skipped, processing continues.

`pax-filename`	is the pax archive file that contains the invalid file record.
`DSV-name`	is the name of the DSV where the error occurred.
`filename`	is the name of the invalid OSS file.

Cause The A7CINFO file contains a record for an OSS file that is in the /G or /E directory. DSM/SCM does not support OSS files in these directories.

Effect The activity finishes with warnings. The DSV is not processed as part of the current input.

Recovery This OSS file must be removed from the pax archive file and a new DSV generated. Contact the product vendor. Because the DSV is skipped, you must bring the DSV into DSM/SCM as a separate input. You can then assign both inputs to the same input group through the Planner Interface. If the input is a release version update (RVU) or a software product revision (SPR), contact your service provider and provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details from any generated messages
Supporting documentation such as the $ZPHI EMS logs and trace files (if requested by your service provider)

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.

3009

pax archive file pax-filename in DSV DSV-name contains invalid file filename which has an OSS file type other than Regular File, Directory, Symbolic Link, Hard Link, or FIFO. DSV skipped, processing continues.

`pax-filename`	is the pax archive file that contains the invalid file record.
`DSV-name`	is the name of the DSV where the error occurred.
`filename`	is the name of the invalid OSS file.

Cause The A7CINFO file contains a record for an OSS file that has an invalid file type. DSM/SCM supports only file types of Regular File, Directory, Symbolic Link, Hard Link, or FIFO.

Effect The activity finishes with warnings. The DSV is not processed as part of the current input.

Descriptions of the problem and accompanying symptoms
Details from any generated messages
Supporting documentation such as the $ZPHI EMS logs and trace files (if requested by your service provider)

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.

3010

The DSV subvolume-name file filename has no CNFGINFO entry in A0CINFO. Planner must use NonStop Software Essentials Package Software to update A0CINFO file for DSV and bring it into DSM/SCM as a separate input, then assign two inputs to the same Input Group. DSV skipped, processing continued.

`subvolume-name`	is the name of the distribution subvolume (DSV) where the error occurred.
`filename`	is the file name in the internal format of the DSV file that is not listed in the A0CINFO file.

Cause The A0CINFO file was missing an entry for a file in the DSV.

Effect The activity finishes with warnings. The DSV is not processed as part of the current input.

Recovery The planner should contact the HP representative or the third-party software representative concerning the missing entry to determine whether the file is needed. If the DSV file is not needed, delete the file from the DSV. If the file is needed, use NonStop Software Essentials Package Software to create a new A0CINFO file for the DSV. If you need help completing the correct NonStop Software Essentials Package Software processing, contact the product vendor. Because the DSV has been skipped, you must bring the DSV into DSM/SCM as a separate input. You can then assign both inputs to the same input group through NonStop Software Essentials.

3011

pax archive file pax-filename in DSV DSV-name contains duplicate records for file filename. DSV skipped, processing continues.

`pax-filename`	is the pax archive file that contains the duplicate file records.
`DSV-name`	is the name of the DSV where the error occurred.
`filename`	is the name of the invalid OSS file.

Cause The A7CINFO file contains two records for the same OSS file.

Effect The activity finishes with warnings. The DSV is not processed as part of the current input.

Recovery The duplicate OSS file must be removed from the pax archive file and a new DSV generated. Contact the product vendor. Because the DSV is skipped, you must bring the DSV into DSM/SCM as a separate input. You can then assign both inputs to the same input group through the Planner Interface. If the input is a release version update (RVU) or a software product revision (SPR), contact your service provider and provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details from any generated messages
Supporting documentation such as the $ZPHI EMS logs and trace files (if requested by your service provider)

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.

3012

pax archive file pax-filename in DSV DSV-name contains invalid file filename with a relative path name. Relative path names are not allowed by DSM/SCM. DSV skipped, processing continues.

`pax-filename`	is the pax archive file that contains the invalid file record.
`DSV-name`	is the name of the DSV where the error occurred.
`filename`	is the name of the invalid OSS file.

Cause The pax archive file contains an OSS file with a relative path (the path does not start with a slash “/” character). DSM/SCM does not allow relative path names.

Effect The activity finishes with warnings. The DSV is not processed as part of the current input.

Recovery The relative OSS file must be removed from the pax archive file and a new DSV generated. Contact the product vendor. Because the DSV is skipped, you must bring the DSV into DSM/SCM as a separate input. You can then assign both inputs to the same input group through the Planner Interface. If the input is a release version update (RVU) or a software product revision (SPR), contact your service provider and provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details from any generated messages
Supporting documentation such as the $ZPHI EMS logs and trace files (if requested by your service provider)

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.

3013

pax archive file pax-filename is missing from the A0CINFO file in DSV DSV-name. According to the A0CINFO file, pax-filename contains OSS file filename. DSV skipped, processing continues.

`pax-filename`	is the pax archive file that contains the invalid file record.
`DSV-name`	is the name of the DSV where the error occurred.
`filename`	is the name of the invalid OSS file.

Cause The A7CINFO file contains a record for an OSS file that came from a pax archive file that is not in the DSV. There is no record in the A0CINFO file for the pax archive file.

Effect The activity finishes with warnings. The DSV is not processed as part of the current input.

Recovery The missing pax archive file must be added to the DSV and CNFGINFO run for the DSV to add the missing file to the A0CINFO file. For help completing the correct CNFGINFO processing, contact the product vendor. Because the DSV is skipped, you must bring the DSV into DSM/SCM as a separate input. You can then assign both inputs to the same input group through the Planner Interface. If the input is a release version update (RVU) or a software product revision (SPR), contact your service provider and provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details from any generated messages
Supporting documentation such as the $ZPHI EMS logs and trace files (if requested by your service provider)

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.

3014

pax archive file pax-filename in DSV DSV-name is not placed in the ZOSSUTL TSV. According to the A7CINFO file, pax-filename contains OSS file filename. DSV skipped, processing continues.

`pax-filename`	is the pax archive file that contains the invalid file record.
`DSV-name`	is the name of the DSV where the error occurred.
`filename`	is the name of the invalid OSS file.

Cause The pax archive file, referred to by records in the A7CINFO file, must be placed in the ZOSSUTL TSV. This pax archive file must have specified the ZOSSUTL TSV to create the A7CINFO file. The destination TSV for the pax archive file changed since the A7CINFO file was created.

Effect The activity finishes with warnings. The DSV is not processed as part of the current input.

Recovery Use CNFGINFO to change the TSV for this pax archive file to ZOSSUTL. For help completing the correct CNFGINFO processing, contact the product vendor. Because the DSV is skipped, you must bring the DSV into DSM/SCM as a separate input. You can then assign both inputs to the same input group through the Planner Interface. If the input is a release version update (RVU) or a software product revision (SPR), contact your service provider and provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details from any generated messages
Supporting documentation such as the $ZPHI EMS logs and trace files (if requested by your service provider)

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.

3015

The DSV subvolume-name has an entry in the A0CINFO file for the file filename, which is not in the DSV. DSV skipped, processing continues.

`subvolume-name`	is the name of the distribution subvolume (DSV) where the error occurred.
`filename`	is the file name in the internal format of the missing file.

Cause The A0CINFO file had an entry for a file that was not in the DSV.

Effect The activity finishes with warnings. The DSV is not processed as part of the current input.

Recovery The planner should contact the HP or third-party software representative concerning the missing file to determine whether the file is needed. If the DSV file is not needed, use CNFGINFO to delete the entry in the A0CINFO file for the file that is missing. If the missing file is needed, the planner should obtain a copy of the file and use CNFGINFO to create an entry in the A0CINFO file for the new file. If you need help completing the correct CNFGINFO processing, contact the product vendor. Because the DSV has been skipped, you must bring the DSV into DSM/SCM as a separate input. You might want to get a new DSV. You can then assign both inputs to the same input group through the Planner Interface.

3016

A7CINFO file format error error occurred on record number record of pax archive file pax-filename in DSV DSV-name. OSS file name is oss-filename. DSV skipped, processing continues.

`error`	is one of these A7CINFO format errors: 1: The pax archive file specified in the record should be in the form: /G/dsmscm/md100ga7/t8100px1. No ‘/’ characters were found in this field. 2: The OSS filename in the variable length record should be in the form: dir1/dir2/file. No ‘/’ characters were found in this field. Relative filenames are not allowed. 3: The pax archive file that a link file refers to should be in the form: dir1/dir2/file. No ‘/’ characters were found in this field. Relative filenames are not allowed.
`record`	is the invalid record number in the A7CINFO file.
`pax-filename`	is the pax archive file that contains the invalid file record.
`DSV-name`	is the name of the DSV where the error occurred.
`oss-filename`	is the name of the invalid OSS file.

Cause Invalid data was found in the A7CINFO file.

Effect The activity finishes with warnings. The DSV is not processed as part of the current input.

Recovery Contact the product vendor to re-create the A7CINFO file. Because the DSV is skipped, you must bring the DSV into DSM/SCM as a separate input. You can then assign both inputs to the same input group through the Planner Interface. If the input is a release version update (RVU) or a software product revision (SPR), contact your service provider and provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details from any generated messages
Supporting documentation such as the $ZPHI EMS logs and trace files (if requested by your service provider)

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.

3020

Invalid A0CINFO file detected in DSV subvolume-name. DSV processing skipped.

subvolume-name

is the name of the distribution subvolume (DSV) with the invalid A0CINFO file.

Cause You attempted to input a DSV, but the DSV contained an invalid A0CINFO file. The A0CINFO file might be invalid because it contains corrupt data or because of its file type.

Effect The activity finishes with warnings. The DSV is not processed as part of the current input.

Recovery Use CNFGINFO to update the DSV’s A0CINFO file. If you need help completing the correct CNFGINFO processing, contact the product vendor. Because the DSV has been skipped, you must bring the DSV into DSM/SCM as a separate input. You can then assign both inputs to the same input group through the Planner Interface.

3021

Invalid A1CINFO file detected in DSV subvolume-name. DSV processing skipped.

subvolume-name

is the name of the distribution subvolume (DSV) with the invalid A1CINFO file.

Cause You attempted to input a DSV, but the DSV contained an invalid A1CINFO file. The A1CINFO file might be invalid because it contains corrupt data, an incorrect file type, or an incorrect file version.

Effect The activity finishes with warnings. The DSV is not processed as part of the current input.

Recovery Use CNFGINFO to update the DSV’s A1CINFO file. If you need help completing the correct CNFGINFO processing, contact the product vendor. Because the DSV has been skipped, you must bring the DSV into DSM/SCM as a separate input. You can then assign both inputs to the same input group through the Planner Interface.

3022

The A0CINFO file in DSV subvolume-name is version version, which this version of DSM/SCM cannot read. Processing of this DSV stopped. Upgrade to a newer DSM/SCM version and retry your request.

`subvolume-name`	is the name of the distribution subvolume (DSV).
`version`	is the version of A0CINFO file.
`dsv-name`	is the DSM/SCM version currently running on the system.

Cause You attempted to input a DSV containing a product that uses a version version A0CINFO file. The version of DSM/SCM you are running cannot read version version A0CINFO files.

Effect The input software request stops restartable.

Recovery Install a later DSM/SCM product version that can read version version A0CINFO files, then restart the input software request.

3025

Input input-name does not contain DSM/SCM product. Contact HP.

input-name

is the name specified for the software input.

Cause The DSM/SCM product was not found on the specified SUT.

Effect If you copy this input to a new configuration revision, DSM/SCM is removed from the new revision.

Recovery Contact your service provider or your third-party software distributor to determine why DSM/SCM is not on the SUT. Provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as the $ZPHI Event Management Service (EMS) logs and trace files (if requested by your service provider)

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.

3030

The A a-site-id subvolume subvolume-name has invalid/missing RLSEID/CUSTFILE files. Contact HP.

`a-site-id`	is the name of the first subvolume on the site update tape (SUT).
`subvolume-name`	is the name of the subvolume containing the invalid files.

Cause You attempted to input a SUT with invalid or missing RLSEID or CUSTFILE files.

Effect The activity stops in a restartable state.

Recovery Contact your service provider and provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as the $ZPHI Event Management Service (EMS) logs and trace files (if requested by your service provider)

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.

3031

Another software input is in progress. This Receive-All-Files software input cannot be started or cancelled when other software input requests are in progress. Restart this request after all the other software inputs are complete.

Cause A software input request with the Receive-All-Files option was started while another software input request was already being processed.

Effect DSM/SCM cannot process the input.

Recovery Wait until the other software input has completed, then restart the request.

3032

A Receive-All-Files software input is in progress. No other software inputs can be received or cancelled until the Receive-All-Files software input completes. Restart this request after the Receive-All-Files software input completes.

Cause A software input request was started while a Receive-All-Files software input request was already being processed.

Effect DSM/SCM cannot process the input.

Recovery Wait until the Receive-All-Files software input has completed, then restart the request.

3035

Invalid SUT version software-version. DSM/SCM can only accept SUTs for Release C30.10/D20 and later. Ensure you have SUT at correct release level.

software-version

is the NonStop RVU ID.

Cause The SUT contains software at an RVU earlier than C30.10 (C-series RVU) or D20 (D-series RVUs).

Effect DSM/SCM cannot process the input.

Recovery Ensure that you are using a SUT containing the correct RVU (C30.10/D20 or later).

3040

No products were processed for this Software Input.

Cause No products were processed for the software input activity. The error that caused this message appears in the message that precedes this one.

Effect The activity finishes with errors. No products were processed for the software input activity.

Recovery For the recovery procedure, consult the description in this manual of the preceding error message. Correct the error and retry the software input activity.

3045

Specified software input name input-name already exists. Specify another name and process the input again.

input-name

is the name specified for the software input.

Cause You specified a software input name that already exists.

Effect The activity finishes with errors. DSM/SCM does not process the input.

Recovery Start a new activity, specify a different software input name, and process the input again.

3050

Duplicate product in software input. Duplicate DSV subvolume-name skipped, processing continues.

subvolume-name

is the name of the duplicate distribution subvolume (DSV).

Cause The specified DSV corresponded to a product that had already been processed in a previous DSV for this software input.

Effect The activity finishes with warnings. DSM/SCM processes only the first instance of the DSV encountered in the input.

Recovery Contact your service provider or your third-party software distributor to ensure that the correct DSV version has been processed by DSM/SCM. Provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as the $ZPHI Event Management Service (EMS) logs and trace files (if requested by your service provider)

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.

3060

The DSV DSV-name has an inconsistent A0CINFO file. File filename has an incorrect file size.

`DSV-name`	is the name of a distribution subvolume (DSV) in the software input.
`filename`	is the name of the A0CINFO file in the DSV.

Cause The actual file size of the filename file was different from the file size specified in the A0CINFO file itself.

Effect The activity stops in a restartable state.

Recovery Fix the A0CINFO file and restart the activity, or cancel the activity.

3065

The DSV subvolume-name has an inconsistent A7CINFO file. File filename has an incorrect last modification time. To correct, put DSV on disk, run NonStop Software Essentials Package Software on DSV without changing any fields. Repeat Receive software. Report problem to software vendor.

`subvolume-name`	is the name of a distribution subvolume (DSV) in the software input where the error occurred.
`filename`	is the name of the pax file in the DSV that contributed to the error.

Cause The file indicated changed since the A7CINFO file was created.

Effect The Receive Software request stops restartable.

Recovery Cancel the Receive Software request. Get the DSV on disk. Run NonStop Software Essentials Package Software on the DSV without changing any input fields. This command re-creates the A7CINFO file from the current pax file or files. Receive the software into the archive again. Report the problem to your software vendor.

3070

The DSV DSV-name has an A1CINFO file with an unknown file format version. A more recent version of DSM/SCM is required to receive this software.

DSV-name

is the name of a distribution subvolume (DSV) in the software input.

Cause The format of the A1CINFO file in this DSV is not readable by this DSM/SCM PVU. Information included in the A1CINFO file might cause the format of the file to change in the future.

Effect The receive software request stops in a restartable state.

Recovery Cancel the receive software request. Upgrade to the latest DSM/SCM PVU and restart the request.

3071

The DSV DSV-name has an A7CINFO file with an unknown file format version. A more recent version of DSM/SCM is required to receive this software.

DSV-name

is the name of a distribution subvolume (DSV) in the software input where the error occurred.

Cause The software being received contains a new version of the A7CINFO file that the current DSM/SCM PVU cannot read.

Effect The receive software request stops in a restartable state.

Recovery Cancel the receive software request. Upgrade to the latest DSM/SCM PVU and restart the request.

3080

WARNING: The DSV DSV-name requires the Capability-name capability to be installed correctly. The Product-version and later versions of DSM/SCM have this capability. If this DSV can not be received then the Product-version or later version of DSM/SCM must be used to receive this software.

`DSV-name`	is the name of the distribution subvolume (DSV) in the software input.
`Capability-name`	is the name of the capability required.
`Product-version`	is the minimum DSM/SCM product version that supports this capability.

Cause The information in the A1CINFO file in this DSV indicates that a specific capability is required to correctly install this product. The current DSM/SCM PVU that is receiving this software does not have this capability.

Effect If all the information in the A1CINFO file can be received, this product will be received successfully. If all the information in the A1CINFO file for this DSV cannot be received, the request will not complete successfully.

Recovery Upgrade to the indicated DSM/SCM PVU and restart the request.

3090

Receive software software is obsolete and cannot be received into the archive on a processor-type-host host.

`Receive software`	is the processor type of the received software.
`processor-type`	is the processor type of the host system.

Cause Receive software for TNS/TNSR software was performed on TNSX host.

Effect The activity stops restartable.

Recovery Correct the software processor type to be received using NonStop Software Essentials Package Software.

4010

Error file-error accessing scratch volume volume-name. Correct problem indicated in error. RESTART activity.

`file-error`	is the file-system error that occurred. For file-system error definitions, see the Guardian Procedure Errors and Messages Manual.
`volume-name`	is the name of the scratch volume that could not be accessed.

Cause DSM/SCM could not access the specified scratch volume on the target scratch list.

Effect The activity stops in a restartable state.

Recovery Check the file-system error code in the message. For more information, including recovery actions, see the Guardian Procedure Errors and Messages Manual. Correct the error based on the recovery specified for the file-system error. Restart the activity.

4015

DSM/SCM does not allow user extensions to the standard defines in the STANDARD_MICROCODE, SYSTEM_PROCESS_LIBRARY_FILES, SYSTEM_LIBRARY_CODE_FILES, SYSTEM_PROCESS_CODE_FILES, FILES_TO_COPY_TO_NEW_SYSTEM sections of the SYSGEN configuration file. Add the additional software to the revision before requesting a build.

Cause Files have been added to one or more of the indicated defines sections of the CONFTEXT file. DSM/SCM does not let files be added to a revision through the CONFTEXT file.

Effect DSM/SCM stops and issues this message.

Recovery Remove the file names from the CONFTEXT file. The files must be brought into the archive as inputs, then added to the software revision before you request that the revision be built.

4016

File file-name from product product-number has invalid file function file-function for the target processor type. Cancel the Build, correct the product in a new revision, and perform another Build.

`file-name`	is the file name of the product which has invalid file function.
`product-number`	is the product number which contains the file with invalid file function.
`file-function`	is the invalid file function for Cognac.

Cause File function of the file is one of the obsolete implicit DLL file function CORE, ETC or FS.

Effect The Build activity stops in non restartable stage.

Recovery The planner should cancel the Build activity. Re-create the product by changing the appropriate file function for Cognac, receive it in software archive, include (copy) in the new revision and Build the new revision.

4020

Current database information for operator activation instructions out of sync with request information.

Cause The Configuration Builder and the Planner Interface received conflicting database information regarding operator activation instructions. Possibly a new system snapshot has been received, the CONFTEXT file has been changed, or database corruption has occurred.

Effect The activity finishes with errors.

Recovery Try to start a new Build or Build/Apply activity. If the error recurs, the database is suspect. Contact your service provider and provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as the $ZPHI Event Management Service (EMS) logs and trace files (if requested by your service provider)

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.

4030

Release level software-release-level of configuration revision configuration-name is not supported by DSM/SCM.

`software-release-level`	is the name of the internal NonStop software release ID.
`configuration-name`	is the name of the configuration you are trying to build.

Cause DSM/SCM could not build the revision because it was created from a site update tape (SUT) containing an internal HP (Xnn) release.

Effect The activity completes with errors.

Recovery Re-create the software revision using a SUT that contains a valid RVU.

4031

product-file contains OSS files that will be managed by DSM/SCM and OSS files that will not be managed by DSM/SCM. pax file filename is one of the pax archive files that contains OSS files that will be managed by DSM/SCM.

`product-file`	is the product number that is partially OSS-enabled for DSM/SCM.
`filename`	is the name of one of the pax archive files that DSM/SCM will install the OSS files from.

Cause The product likely contains a base version and several overlaid SPRs, not all of which are DSM/SCM-enabled.

Effect DSM/SCM does not manage the OSS files in the pax archive files listed in the subsequent event message 4032. The Build completes with warnings.

Recovery Use PINSTALL to install the OSS files in the pax archive file that are not DSM/SCM-enabled.

4032

The OSS files, associated with the following pax archive files in ZOSSUTL, will not be installed by DSM/SCM because they are not DSM/SCM enabled: pax-file-list. Use PINSTALL to install the OSS files from these pax archive files.

pax-file-list

is the name of one or more pax archive files for OSS products that are not DSM/SCM-enabled.

Cause The specified pax archive files are not DSM/SCM-enabled. All pax archive files released by HP starting with the G06.18 RVU are DSM/SCM-enabled. DSM/SCM-enabled pax archive files are accompanied by an A7CINFO file in the DSV.

Effect DSM/SCM does not manage the OSS files listed in the pax archive files. The Build completes with warnings.

Recovery After you activate the configuration with ZPHIRNM, use PINSTALL to install the OSS files in the pax archive.

4033

The following OSS products either have unprocessed A7CINFO files, or contain non-pax files in ZOSSUTL: product-list. To process the A7CINFO files, re-receive these products into the archive using the Receive All Files option. Use NonStop Software Essentials Package Software to remove any non-pax files from ZOSSUTL. CANCEL Build. Perform another Build request.

product-list

is one or more product numbers.

Cause The listed products either were received into the Archive by a pre-D46 PVU of DSM/SCM or contain non-pax files (filecode not 0 or 180) in the ZOSSUTL TSV.

Effect The Build stops. The A7CINFO files must be processed before DSM/SCM can manage these OSS files.

Recovery Cancel the build request. Either use the D46 or later DSM/SCM PVU to receive these products into the Archive again using the Receive All Files option, or clear the Manage OSS Files check box for this logical target. Perform another build. If the product contains non-pax files in the ZOSSUTL TSV, use NonStop Software Essentials Package Software to re-create the TSV for the non-pax file. If you need help completing the correct NonStop Software Essentials Package Software processing, contact the product vendor.

4035

No DSM/SCM enabled OSS products found(no A7CINFO files) in the configuration. CANCEL the Build, Remove OSS management from this Logical Target, and perform another Build.

Cause You indicated that the logical target associated with this Build is to manage OSS files, but the configuration contains no DSM/SCM-enabled OSS products.

Effect The Build stops restartable because the operator instructions generated for this Build are incorrect if OSS files are not managed by DSM/SCM.

Recovery Cancel the Build. Clear the Manage OSS Files check box for this logical target, and perform a new Build.

4040

WARNING: SRL mismatch, num1 relocatable files versus num2 executable files.

`num1`	is the number of shared run-time library (SRL) relocatable files in the configuration.
`num2`	is the number of SRL executable files in the configuration.

Cause The number of SRL relocatable files does not match the number of SRL executable files.

Effect The Build continues. This configuration might have a problem with its SRL files.

Recovery Verify that the SRL files were built and placed correctly.

4050

More than one SRL ZTILT source file exists.

Cause The configuration being built contains more than one ZTILT source file.

Effect The Build stops nonrestartable.

Recovery Cancel the Build, remove all but one ZTILT source file from the configuration, and start a new Build.

4060

WARNING: The file SRL-exec-file from product Product-version is an SRL executable file for which no corresponding SRL executable was built by DSM/SCM. The file will not be placed.

`SRL-exec-file`	is an SRL executable file.
`Product-version`	is the product version for the SRL executable file.

Cause This product did not release an SRL relocatable file that DSM/SCM could use to build a corresponding SRL executable.

Effect The Build continues.

Recovery If the indicated SRL file is needed, get a version of this SRL that contains an SRL relocatable that DSM/SCM can build an SRL executable with.

4070

WARNING: The file filename from product Product-version conflicts with an SRL executable file that was built by DSM/SCM. The file will not be placed.

`filename`	is a file name.
`Product-version`	is the product version of the file.

Cause The specified file and product conflicts with an SRL file. Both of the files have the same name and are requesting to be placed in the same subvolume.

Effect The Build continues.

Recovery Determine the cause of the conflict, correct the configuration, and repeat the Build.

4080

The number of SRL relocatable and ZTILT files, num1, does not match the number of SRL executable and ZTILT files, num2, that were built by DSM/SCM.

`num1`	is the number of SRL relocatable files.
`num2`	is the number of SRL executable files produced from the Build.

Cause The SRL build was not successful. For each SRL relocatable, one SRL executable and one ZTILT file should be produced.

Effect The Build stops nonrestartable.

Recovery Determine why there is not a sufficient number of SRL executables. The working subvolumes that DSM/SCM uses to build SRLs are named ZASRL*. One of these subvolumes contains a file named SRLBLDOF, which contains the output from NSKCOM when the SRLs were built. Cancel the Build, correct the problem, and start a new Build.

4090

The SRL relocatable file SRL-rel-file referred to in the SRL log file could not be found in the configuration.

SRL-rel-file

is the name of the SRL relocatable file indicated in the NSKCOM output file named ZASRL*.SRLBLDOF.

Cause This file was not one of the SRL relocatable files specified in the IN file to NSKCOM, but the information retrieved from the NSKCOM OUT file indicates that it was.

Effect The Build stops nonrestartable.

Recovery Determine why the files do not match by examining the NSKCOM output file, which is located on one of the scratch volumes in ZASRL*.SRLBLDOF. Cancel the Build, correct the problem, and start a new Build.

4100

The SRL executable file SRL-exe-file referred to in the SRL log file could not be found in the build subvolume subvolname.

`SRL-exe-file`	is the name of the SRL executable file indicated in the NSKCOM output file ZASRL*.SRLBLDOF.
`subvolname`	is the name of the SRL build subvolume where the SRL executable files were built.

Cause This file was not found in the Build subvolume. It should have been created by the SRL build.

Effect The Build stops nonrestartable.

Recovery Examine the NSKCOM output file, which is located on one of the scratch volumes in ZASRL*.SRLBLDOF, to determine why the file was not created. Cancel the Build, correct the problem, and start a new Build.

4110

server-process completed server-completion-code. Examine server warning(s)/error(s) in file log-file, correct error(s) if necessary, RESTART activity if stopped in a restartable state.

server-process

is NSKCOM.

server-completion-code

is the server completion status of the activity. Possible values:

with error(s)

log-file

is the output file from the server.

Cause NSKCOM has completed an activity for DSM/SCM. The activity has completed successfully, with warnings, or with errors.

Effect Depending on the completion status, either NSKCOM completed processing the activity (if the server completes successfully or with warnings) or stopped processing the activity (if the server stops with errors). If NSKCOM stops with errors, the activity is in a restartable state.

Recovery The recovery procedure depends on the value of the returned server completion code:

If NSKCOM completes the activity successfully, this is an informational message only; no corrective action is needed.
If NSKCOM completes the activity with warnings, the operator should examine the messages from the server process and any appropriate output files to determine if corrective action is needed. (SYSGEN/R always finishes with warnings.) If corrective action is needed, correct the error and start a new activity.
If NSKCOM completes the activity with errors, the operator should examine the messages from the NSKCOM and any appropriate output files to determine the corrective action needed. Correct the error then either cancel the activity and resubmit it after the corrections have been made, or restart the activity.

4116

Public DLL build required because: reason.

reason

indicates the reason why a public DLL build is required. For example:

FORCE-PUBLIC-DLL-BUILD parameter specified
Never been built
ZIMPIMP changed
XIMPIMP changed
ZCOBDLL (T1234) added
ZCOBDLL (T1234) removed
ZCOBDLL (T1234) changed

Cause A public DLL was required for the reason indicated.

Effect The set of public DLLs is built.

Recovery Informational message only; no corrective action is needed.

4120

Invalid SRL build output file Filename in the build subvolume Subvolname.

`Filename`	is the name of the SRL build output file created during the SRL build.
`Subvolname`	is the name of the subvolume where the SRL build output file is located.

Cause An inconsistency occurred in the SRL build output file. The expected sequence of INFO SRL commands and associated output was not found.

Effect The Build stops nonrestartable.

Recovery Examine the specified SRL build output file to determine why the INFO SRL command failed. There should be one INFO SRL command line for each SRL relocatable that is being built, followed by an output line of the relocatable name and its executable name. All the INFO SRL commands are framed by comments of “##### SRL INFO SECTION #####” and “##### END INFO SECTION #####”. Cancel the Build, correct the problem, and start a new Build.

4130

Invalid SRL executable name in the SRL build output file Filename in the build subvolume Subvolname.

`Filename`	is the name of the SRL build output file created during the SRL build.
`Subvolname`	is the name of the subvolume where the SRL build output file is located.

Cause An inconsistency occurred in the SRL build output file. The expected executable name was not there or contained too many characters.

Effect The Build stops nonrestartable.

Recovery Examine the specified SRL build output file to determine why the INFO SRL command failed. There should be one INFO SRL command line for each SRL relocatable being built, followed by an output line of the relocatable name and its executable name. All the INFO SRL commands are framed by comments of “##### SRL INFO SECTION #####” and “##### END INFO SECTION #####”. Cancel the Build, correct the problem, and start a new Build.

4140

Invalid SRL relocatable name in the SRL build output file Filename in the build subvolume Subvolname.

`Filename`	is the name of the SRL build output file created during the SRL build.
`Subvolname`	is the name of the subvolume where the SRL build output file is located.

Cause An inconsistency occurred in the SRL build output file. The expected relocatable name was not there or contained too many characters.

Effect The Build stops nonrestartable.

4150

The SRL ZTILT source file does not exist.

Cause DSM/SCM is attempting to build the SRL executable files. A ZTILT source file is required to build but cannot be found in the configuration. The ZTILT source file should be supplied as file TPRETILT in product T7898. This can occur if:

The ZTILT source file was not included in the configuration properly, or
A product that releases SRLs has incorrectly released an A1CINFO file on a SUT that does not support SRL builds.

Effect The Build stops in a nonrestartable state.

Recovery Cancel the Build. If the T7898 product was not included in the configuration, add it to the next configuration to be built. To determine if a product has released a bogus A1CINFO file, you can generate a Software Product Files report and search for A1CINFO. In the second situation, the products where these files turn up might need SPRs to fix this.

4151

WARNING: number-of-files relocatable SRL(s) found in the processor-type configuration. SRLs are not valid for a processor-type configuration. These files will be excluded. The first file is srl-file-name.

number-of-files

is the number of SRL relocatable files in the configuration.

srl-file-name

is the name of the SRL file.

processor-type

is the CPU type of the system; for example:

TNSE

Cause Relocatable shared-runtime libraries (SRLs) were found in a processor-type configuration.

Effect DSM/SCM ignores these files. SRLs are not used for processor-type systems.

Recovery Informational message only; no corrective action is needed.

4152

WARNING: Executable SRL found in the processor-type configuration. SRLs are not valid for a processor-type configuration. This file will be excluded. The file is srl-file-name(product-number).

srl-file-name

is the name of the SRL file.

product-number

is the number of the product.

processor-type

is the CPU type of the system; for example:

TNSE

Cause Executable shared-runtime libraries (SRLs) were found in a processor-type configuration.

Effect DSM/SCM ignores these files.

Recovery Informational message only; no corrective action is needed.

4153

No public DLL loadfiles were found in the processor-type configuration. A processor-type configuration requires public DLL loadfiles. CANCEL Build. Create a new corrected revision.

processor-type

is the CPU type of the system; for example:

TNSE

Cause No public dynamic-link library (DLL) loadfiles were found in a TNS/X configuration.

Effect Build will stop in non-restartable stage.

Recovery Cancel the Build and create a new corrected revision including the public DLL loadfiles.

4155

One or more products in the Configuration being built has been backed up to tape. Restore the tape in the Software Archive and restart the activity.

Cause DSM/SCM is attempting to build a configuration in which one or more products have been backed up to tape.

Effect The Build stops in a restartable state.

Recovery Restore the software input from the tape to the software archive, then restart the Build/Apply request.

4160

WARNING: Internal error. A duplicate Product product-number was found. This product will be processed normally once. The duplicate entry will be ignored.

product-number

is the number identifier for the duplicated product.

Cause A single product is present in two different inputs.

Effect The second occurrence of the product is discarded.

Recovery This is a warning message. The Build/Apply continues unaffected. No recovery is necessary.

4170

ERROR: A duplicate file was found. Product first-product-number and Product second-product-number both place file filename in TSV subvolume-name. These two files have different fingerprints.

`first-product-number`	is the number identifier for the first occurrence of the duplicated product.
`second-product-number`	is the number identifier for the second occurrence of the duplicated product.
`filename`	is the name of the file that both products refer to.
`subvolume-name`	is the target subvolume where the file is to be placed.

Cause Two products are attempting to place a file with the same name in the same subvolume. These two files have different fingerprints.

Effect The Build stops nonrestartable.

Recovery Create a new configuration and remove one of the two conflicting products.




	NOTE: If the configuration contains conflicting duplicate product files for the stages Processing of TACLSEGF, Processing of MIGRATION TOOLS, and Processing of MISSING FILES, the BUILD activity stops with an error message that displays the product number as ????? or BAAAA.

4171

ERROR: A duplicate OSS file was found. Product first-product-number (first-paxfile) and Product second-product-number (second-paxfile) both place file filename. These two files have different fingerprints or file types.

`first-product-number`	is the product number for the first occurrence of the duplicated product.
`first-paxfile`	is the name of the pax archive file that contains the OSS file for the first occurrence of the duplicated product.
`second-product-number`	is the product number for the second occurrence of the duplicated product.
`second-paxfile`	is the name of the pax archive file that contains the OSS file for the second occurrence of the duplicated product.
`filename`	is the name of the file that both products refer to.

Cause Two products are attempting to place a file with the same name in the same subvolume. These two files have different fingerprints or file types.

Effect The Build stops nonrestartable.

Recovery Cancel the Build activity, create a new configuration, and remove one of the two conflicting products. Perform the Build again. Report the problem to the software vendor.

4180

ERROR: A duplicate file was found. Product first-product-number and Product second-product-number both place file filename in TSV subvolume-name. These two files have the same fingerprints. One file is used. The duplicate file will be ignored.

`first-product-number`	is the number identifier for the first occurrence of the duplicated product.
`second-product-number`	is the number identifier for the second occurrence of the duplicated product.
`filename`	is the name of the file that both products refer to.
`subvolume-name`	is the target subvolume where the file is to be placed.

Cause Two products are attempting to place a file with the same name in the same subvolume. These two files have the same fingerprints.

Effect The second occurrence of the duplicate file is discarded, and the Build continues.

Recovery This is a warning message. No recovery is necessary.

4181

WARNING: A duplicate OSS file was found. Product first-product-number (first-paxfile) and Product second-product-number (second-paxfile) both place file filename. These two files have the same fingerprint. The file from first-product-number (first-paxfile) will be used. The file from second-product-number (second-paxfile) will be ignored.

`first-product-number`	is the product number for the first occurrence of the duplicated product.
`first-paxfile`	is the name of the pax archive file that contains the OSS file for the first occurrence of the duplicated product.
`second-product-number`	is the product number for the second occurrence of the duplicated product.
`second-paxfile`	is the name of the pax archive file that contains the OSS file for the second occurrence of the duplicated product.
`filename`	is the name of the file that both products refer to.

Cause Two products are attempting to place a file with the same name in the same subvolume. These two files have the same fingerprints.

Effect The second occurrence of the duplicate file is discarded, and the Build continues. Some file attributes, in particular the security settings, might conflict between the two definitions. The security settings and other file attributes from the indicated product and pax archive file are used.

Recovery Ensure that the file has the appropriate security and attributes after the configuration is activated (after ZPHIRNM is run).

4190

WARNING: Internal error on read of verification list file. Verification will be partial with regard to restart.

Cause An error occurred reading verified instructions from the restart verification list.

Effect Verification is not performed against the instructions that could not be read from the list file. All instructions left to verify are verified against what was recovered from the list file.

Recovery This is a warning message. No recovery is necessary.

4200

WARNING: Internal error on write of verification list file. A restart will result in partial verification.

Cause An error occurred writing to the verification list file.

Effect An attempt to close the verification list file is made. Any instructions verified after this are not written to the list file. If a restart occurs before all activation package instructions have been verified, the instructions that could not be written to the list file—as well as any that might be lost attempting to open and read the list file—cannot be verified against remaining instructions.

Recovery This is a warning message. No recovery is necessary.

4210

WARNING: Internal error on open of previous restart verification list file. Only partial verification possible.

Cause An error occurred opening the file for instructions verified before restart.

Effect The activation package instructions left to be verified are not checked against the previously verified instructions.

Recovery This is a warning message. No recovery is necessary.

4220

WARNING: Internal error on open of verification list file. A restart will result in partial verification.

Cause An error occurred opening the file for instructions that will be saved for restart.

Effect If a restart occurs before the activation package instructions have all been processed, the remaining instructions cannot be verified against the instructions processed before the restart.

Recovery This is a warning message. No recovery is necessary.

4230

WARNING: File filename is not in the archive, file system error error-number. There were a total of number-archive-files archive files that were not found. Subsequent attempts to access these archive files will cause the request to fail.

`filename`	is the name of the first file found missing from the archive.
`error-number`	is the file-system error with respect to the first missing file.
`number-archive-files`	is the number of files found missing from the archive.

Cause Activation package files are missing from the archive.

Effect If the Build attempts to access one of the missing files, an error occurs.

Recovery This is a warning message. No recovery is necessary. If the Build does not attempt to access a missing archive file, that product will have to be input into the archive.

4240

Check for Labeled Tape operator messages in the system EMS log.

Cause DSM/SCM is writing an activation package to a labeled tape as requested by the user. Check the system EMS log for any labeled tape operator messages.

Effect Informational message only; no corrective action is needed.

Recovery Informational message only; no corrective action is needed.

4250

WARNING: You must restore the labeled Activation Tape onto the target system and do the apply from disk.

Cause DSM/SCM finished building a configuration, putting its activation package onto a labeled tape. The Apply process cannot read an activation package directly from a labeled tape.

Effect The activation package cannot be applied until it is restored to disk.

Recovery Use Restore to restore the activation package from the labeled tape onto the target system, then perform the Apply.

4260

Running SYSGEN.

Cause DSM/SCM is ready to run a system generation program because system generation is required for the current Build.

Effect Informational message only; no corrective action is needed.

Recovery Informational message only; no corrective action is needed.

4261

Internal Error: DSM/SCM cannot find the manufactured build-output-file file in the processor-type configuration. CANCEL Build. Perform another Build request that requires a sysgen.

processor-type

is the CPU type of the system; for example:

TNSE

build-output-file

is the name of the build output file; for example:

ZIMPIMP/XIMPIMP

Cause The build-output-file file is not found in the processor-type configuration in the host database.

Effect The Build stops in non-restartable stage.

Recovery Cancel the Build. Perform another Build request that requires system generation. You can force system generation by changing the CONFTEXT file with a comment.

4262

Configuration-revision is based on a release-version-update SUT. This conflicts with the CPU type which was set as processor-type in the system maintenance profile.

configuration-revision

is the name of the configuration revision you are trying to build; for example:

\CRONUS DEFAULT 10

release-version-update

is the release of the SUT used for building a configuration; for example:

G06.23

processor-type

is the processor type of the system; for example:

TNS/E

Cause You used either a Gxx.xx RVU to build a configuration for a TNS/E or TNS/X target or a Hxx.xx was used to build a configuration for a TNS/R or TNS/X target or Lxx.xx SUT was used to build a configuration for a TNS/E or TNS/R target.

A Gxx.xx SUT is intended only for a TNS/R.
An Hxx.xx SUT is intended only for a TNS/E.
An Lxx.xx SUT is intended only for a TNS/X.

Effect The Build stops restartable.

Recovery Cancel the Build request. Re-create another configuration revision using the correct SUT.

4263

Target processor type processor-type is not supported on a processor-type host.

`processor-type-target`	is the processor type of the target system.
`processor-type-host`	is the processor type of the host system.

Cause Build for TNS/TNSR processor type was performed on TNSX host.

Effect The activity stops non restartable.

Recovery Cancel the activity. Perform another activity with correct host — target pair.

4270

Running SYSGEN (with SIT creation).

Cause DSM/SCM is ready to run a system generation program because system generation is required for the Build, and the user has requested a SIT be created. When the message “DSM/SCM COMPLETED FOR DSM/SCM” appears, the SIT creation has completed as well.

Effect Informational message only; no corrective action is needed.

Recovery Informational message only; no corrective action is needed.

4280

Running SYSGEN (because of SIT creation).

Cause System generation is not required for the current Build, but a request has been made to create a SIT. In this case, DSM/SCM does not have the necessary files to create the SIT itself and needs to run a system generation program to create those files. When the message “DSM/SCM COMPLETED FOR DSM/SCM” appears, the SIT creation has completed as well.

Effect Informational message only; no corrective action is needed.

Recovery Informational message only; no corrective action is needed.

4282

error-type file-system-error on action-code of file/process spooler. Spooling of CONFLIST file will be skipped.

`error-type`	indicates whether the error is restartable or is a warning. This message is a warning.
`file-system-error`	is the file-system error that occurred. File-system errors are defined in Appendix B of the DSM/SCM Event Management Programming Manual..
`action-code`	is the procedure or action during which the error occurred; for example, OPEN. For a list of the possible values, see the description for message 2030.
`spooler`	is the file name of the spooler whose location is being reported.

Cause The spooler was not available when the Build attempted to spool the CONFLIST.

Effect The Build continues without spooling the CONFLIST file.

Recovery None needed. For future Builds, start the spooler if spooling is required.

4285

Unable to create non-essential activation dialout report and continuing.

Cause The creation of the activation dial-out report (SWCONFIG) failed.

Effect The activation dial-out report (SWCONFIG) is not created.

Recovery Informational message only; no corrective action is needed.

4290

Creating activation package.

Cause The DSM/SCM Build process is ready to create the activation package.

Effect Informational message only; no corrective action is needed.

Recovery Informational message only; no corrective action is needed.

4300

SIT tape copy finished.

Cause A DSM/SCM-generated SIT has completed successfully (not activated by a system generation program).

Effect Informational message only; no corrective action is needed.

Recovery Informational message only; no corrective action is needed.

4310

Creating SIT tape copy number number.

number

is the number of the SIT currently being created (can be 1 through 9).

Cause DSM/SCM is creating a SIT copy without the assistance of a system generation program.

Effect Informational message only; no corrective action is needed.

Recovery Informational message only; no corrective action is needed.

5000

Error file-error setting GUARDIAN security attributes for filename to OWNER owner-name, PROTECTION protection, PROGID progid, CLEARONPURGE clearonpurge, LICENSE license. Change the GUARDIAN security attributes on the file. RESTART the activity.

file-error

is the file-system error that occurred. For file-system error definitions, see Guardian Procedure Errors and Messages Manual.

filename

is the file name in the internal format of the file where the error occurred.

owner-name

is the owner of the file.

protection

is the operating system security level assigned to the file.

progid

specifies whether the PROGID attribute for the file is ON or OFF.

clearonpurge

specifies whether the CLEARONPURGE attribute for the file is ON or OFF.

license

specifies whether the file is licensed:

OFF

Cause An error occurred in setting an operating system security attribute on the specified file.

Effect The activity stops in a restartable state.

Recovery Check the file-system error code in the message. For more information, including recovery actions, see the Guardian Procedure Errors and Messages Manual. Change the operating system security attributes of the file so that DSM/SCM can access it. Restart the activity.

5005

Error sfg-error setting SAFEGUARD security attributes for filename like the file like-filename. Change the SAFEGUARD security attributes on the file. RESTART the activity.

`sfg-error`	is the Subsystem Programmatic Interface (SPI) error that occurred on a command to the Safeguard subsystem. Safeguard SPI errors are defined in the Safeguard Management Programming Manual.
`filename`	is the file name in the internal format of the file whose Safeguard attributes are being set.
`like-filename`	is the file name in the internal format of the file whose Safeguard attributes are being duplicated.

Cause An error occurred setting the Safeguard security attributes of one file to match those of another file.

Effect The activity stops in a restartable state.

Recovery Check the error code in the message. For a definition and recovery action for the specified error, see the Safeguard Management Programming Manual. Change the Safeguard security attributes on the file whose attributes must be set by DSM/SCM so that DSM/SCM can correctly set the Safeguard security attributes. Restart the activity.

5010

TSV volume primary-volume-name alternate-volume-name not online. Verify Database for target-name skipped. Ensure TSVs to verify are online.

`primary-volume-name`	is the name of the primary target subvolume (TSV) volume.
`alternate-volume-name`	is the name of the alternate TSV volume.
`target-name`	is the system name of the target.

Cause A Target Interface request to perform a Verify Database activity included a TSV that was not online. DSM/SCM cannot process volumes that are not online.

Effect DSM/SCM skips processing the target and continues with the next target.

Recovery Check that the correct volume was specified. If so, check that the drive is up and accessible. Resubmit another Verify Database activity for the target.

5012

This configuration, for target system-name, installs OSS files into the OSS environment. OSS is not started with the root fileset mounted. Start OSS and RESTART the activity.

system-name

is the name of the logical target for which the configuration is being applied.

Cause The OSS Name Server for the root fileset ($ZPNS) is not running.

Effect The Apply stops in a restartable state.

Recovery Start the root name server ($ZPNS) and then restart the Apply request.

5014

DSM/SCM will install OSS files for target system-name.

system-name

is the name of the logical target for which the configuration is being applied.

Cause The Manage OSS Files check box for this target is checked, and the configuration qualifies for OSS file management.

Effect OSS files are installed and managed by DSM/SCM for this logical target.

Recovery Informational message; no corrective action is necessary.

5015

Cannot BACKOUT configuration configuration-name, reason. Ensure there is a previously saved configuration before you attempt to BACKOUT a configuration.

configuration-name

is the name of the configuration to which you are trying to back out.

reason

is the reason the Backout could not be performed. Possible values:

not most recently applied

no backup exists

Cause You are trying to perform a Backout, but DSM/SCM cannot find a previously saved configuration. Either a Backout has already been performed, or the previous configuration was incorrectly specified.

Effect The activity finishes with errors. DSM/SCM does not perform a Backout.

Recovery Check that a previous configuration exists and that its location is correctly displayed on the Backout—Verify Request screen in the Target Interface; then resubmit another Backout activity for the target.

5020

Insufficient disk space exists for APPLY/BACKOUT of configuration config-name. Space required: space-required bytes, space exists: space-exists bytes, volume volume-name. Correct the error by freeing up space on the volume disk. RESTART the activity.

`config-name`	is the name of the configuration where the error occurred.
`space-required`	is the amount of disk space (in bytes) required to execute the Apply or Backout activity.
`space-exists`	is the amount of disk space (in bytes) available on the specified volume to perform the Apply or Backout activity.
`volume-name`	is the name of the volume where the error occurred.

Cause Not enough space was available on the volume specified to execute an Apply or Backout activity for the specified configuration.

Effect The activity stops in a restartable state.

Recovery Free space on the specified volume, or cancel the request and resubmit it specifying a different work volume on the Maintenance Interface.

5021

DSM/SCM has detected that the new filename file is different (fingerprint) from the file in SYSnn sysnum. The OVERRIDE-SYSNN param (and possibly OVERRIDE-SYSNN-DIFFERENT-OS params) has been specified to allow the APPLY to go to SYSnn sysnum anyway. The existing file in SYSnn sysnum will be retained.

`filename`	is the name of the file manufactured by a system generation program.
`sysnum`	is the octal number of the currently executing SYS`nn`.

Cause DSM/SCM detected that the new file manufactured by a system generation program is different from the one in the executing SYSnn. OVERRIDE parameters were specified to ignore the difference and continue processing.

Effect The Apply continues.

Recovery No action is required.

5022

OVERRIDE SYSnn not allowed because the host system is not running DSM/SCM version T6031AAX or later

Cause The DSM/SCM product version update (PVU) of the host system is not T6031AAX or later.

Effect The Apply stops restartable.

Recovery Install T6031AAX or later on the host system.

5023

DSM/SCM has detected that the new filename file is different (fingerprint) from the existing filename file in SYSnn sysnum. The OVERRIDE-SYSNN param has been specified to allow the APPLY to go to SYSnn sysnum anyway. However, a change in this file indicates that the OS has really changed. If you specify the OVERRIDE-SYSNN-DIFFERENT-OS param and restart the request, the existing file will not be replaced. Otherwise, either coldload from a different SYSnn and RESTART the activity, or CANCEL this activity and START a new APPLY specifying a different target SYSnn.

`filename`	is the name of the file manufactured by a system generation program.
`sysnum`	is the octal number of the currently executing SYS`nn`.

Cause DSM/SCM detected that the new file manufactured by a system generation program is different from the one in the executing SYSnn. OVERRIDE parameters were not specified to ignore the difference.

Effect The Apply stops restartable.

Recovery You have three alternatives:

To force the Apply to the same SYSnn and not place the new file manufactured by a system generation program, specify this OVERRIDE Pathway parameter to the Target Activator (TA):
PATHCOM $YPHI =Alter TA-001, param OVERRIDE-SYSNN-DIFFERENT-OS 'logical_target_nameRevision'.
For example, if the name of the logical target is default and the configuration revision number is 19, the logical-target-nameRevision value to pass is default19. There is no space between the configuration name and the revision number, and the parameter is not case-sensitive.
Perform a system load from a different SYSnn and then restart the activity.
Cancel the Apply and then start a new Apply request specifying a different target SYSnn.

5024

OVERRIDE-SYSNN specified. File filename has changed and will be replaced in the running SYSnn.

filename

is the name of the file manufactured by a system generation program.

Effect The Apply continues.

Recovery No action is required.

5025

Cannot proceed, cannot replace sysnn-type SYSnn sysnn-num. Either coldload a different SYSnn and RESTART the activity or CANCEL this APPLY and start a new APPLY specifying a different target SYSnn.

`sysnn-type`	is the current configuration SYS`nn`.
`sysnn-num`	is the octal number of the current configuration SYS`nn`.

Cause An Apply activity could not finish because it tried to replace the current configuration SYSnn.

Effect The activity stops in a restartable state.

Recovery The recovery steps depend on the situation:

Perform a system load from a different SYSnn; then restart the activity.
Cancel this Apply; then start a new Apply request specifying a different target SYSnn.

5026

DSM/SCM has detected that the OSIMAGE file is different from the currently executing OSIMAGE file in SYSnn sysnn-num. If you know that the new OSIMAGE file is really the same as the ‘currently executing’ OSIMAGE file, you can force the APPLY to adopt the ‘currently executing’ OSIMAGE by specifying OVERRIDE Pathway params and RESTART the APPLY. Otherwise, either coldload from a different SYSnn and RESTART this activity, or CANCEL this activity and START a new APPLY specifying a different target SYSnn.

sysnn-num

is the octal number of the currently executing SYSnn.

Cause The Apply is not replacing the OSIMAGE in the target SYSnn because it is currently executing. You probably passed the OVERRIDE-SYSNN parameter incorrectly, or its parameter value does not match the expected value.

Effect The Apply stops in a restartable state.

Recovery You have three alternatives:

Perform a system load from a different SYSnn; then restart the activity.
Cancel this Apply; then start a new Apply request specifying a different target SYSnn.
To force the Apply to the same SYSnn and ignore the new OSIMAGE that is being made, pass two Pathway parameters to the target activator (TA):
PATHCOM $YPHI =Alter TA-001, param OVERRIDE-SYSNN 'logical-target-nameRevision' =Alter TA-001, param OVERRIDE-SYSNN-DIFFERENT-OS 'logical-target-nameRevision'
For example, for the logical target default with configuration revision number 19, logical-target-nameRevision is default19. There is no space between the configuration name and number, and the parameter is not case-sensitive.
DSM/SCM checks for the OVERRIDE Pathway parameters and matches their values with the configuration revision being applied. If a match occurs, the Apply continues to the specified SYSnn without replacing the OSIMAGE, and no system load is required because the system continues running on the same OSIMAGE. If the parameter is not detected, is incorrect, or does not indicate the configuration revision being applied, the OSIMAGE might be replaced, or an error 5026 might be issued.

5027

DSM/SCM has detected that the OSIMAGE file is different from the currently executing OSIMAGE file in SYSnn sysnn-num. The OVERRIDE-SYSNN and OVERRIDE-SYSNN-DIFFERENT-OS params have been specified to allow the APPLY to go to SYSnn sysnn-num anyway. The new OSIMAGE file and the ‘currently executing’ OSIMAGE file are different sizes. The ‘currently executing’ OSIMAGE file will be retained.

sysnn-num

is the octal number of the currently executing SYSnn.

Cause DSM/SCM detected that the new OSIMAGE file is different from the current OSIMAGE. OVERRIDE parameters were specified to ignore this difference and continue processing.

Effect The Apply continues processing.

Recovery No action is required.

5028

DSM/SCM has detected that the new OSIMAGE file is different from the currently executing OSIMAGE in SYSnn sysnn-num. The OVERRIDE-SYSNN param has been specified to allow the APPLY to go to SYSnn sysnn-num anyway. However, the current OSIMAGE and new OSIMAGE file are different sizes. If you are sure the two OSIMAGE files are the same version, specify the OVERRIDE-SYSNN-DIFFERENT-OS param and restart the request. Otherwise, either coldload from a different SYSnn and RESTART the activity, or CANCEL this activity and START a new APPLY specifying a different target SYSnn.

sysnn-num

is the octal number of the currently executing SYSnn.

Cause An Apply detected that the old and new OSIMAGE files are different versions, and the OVERRIDE-SYSNN-DIFFERENT-OS parameter was not specified to ignore the difference.

Effect The Apply request stops restartable.

Recovery You have three alternatives:

Perform a system load from a different SYSnn and then restart the Apply.
Cancel the Apply and then start a new Apply request specifying a different target SYSnn.
Force an Apply to the same SYSnn and ignore the new OSIMAGE; then specify this OVERRIDE Pathway parameter to the Target Activator (TA):
PATHCOM $YPHI > ALTER TA-001, param 'OVERRIDE-SYSNN-DIFFERENT-OS' 'logical-target-nameRevision'
For example, for the logical target named default with configuration revision number 19, logical-target-nameRevision is default19. There is no space between the configuration name and number, and the parameter is not case-sensitive.

5029

DSM/SCM has detected that the new OSIMAGE file is different from the currently executing OSIMAGE in SYSnn sysnn-num. The OVERRIDE-SYSNN param has been specified to allow the APPLY to go to SYSnn sysnn-num anyway. The new OSIMAGE file and the currently executing OSIMAGE file are the same size. The ‘currently executing’ OSIMAGE file will be retained.

sysnn-num

is the octal number of the currently executing SYSnn.

Cause DSM/SCM detected that the new OSIMAGE file is different from the OSIMAGE file in the currently executing SYSnn, but their EOFs are the same. OVERRIDE-SYSNN parameters were specified to continue processing.

Effect The Apply continues processing.

Recovery No action is required.

5030

ZPHIRNM is running. Cannot proceed with request. Submit the request after the process finishes.

Cause DSM/SCM could not proceed with an activity because you were running the Rename process ($tsv-vol.ZDSMSCM.ZPHIRNM). The activity cannot be run at the same time as the Rename process.

Effect The activity stops in a restartable state.

Recovery Restart the activity after the Rename process finishes.

5031

DSM/SCM has detected that the new OSIMAGE file is same version as the ‘currently executing’ OSIMAGE file in SYSnn sysnn-num. The OVERRIDE-SYSNN param for this configuration is not allowed. Remove the param and restart the request.

sysnn-num

is the octal number of the currently executing SYSnn.

Cause DSM/SCM detected that the new OSIMAGE file is the same version as the current OSIMAGE file. OVERRIDE-SYSNN parameters are not allowed.

Effect The Apply stops restartable.

Recovery Delete the OVERRIDE parameters for this configuration:

Check whether any OVERRIDE parameters are specified for the Target Activator (TA):
PATHCOM $YPHI = INFO TA-001
Delete the OVERRIDE parameters you found in step 1:
= ALTER TA-001, DELETE PARAM param-name
Restart the Apply request.

5035

Security violation error file-error, file filename. Adjust the security on the file so DSM/SCM can access it. RESTART the activity.

`file-error`	is the file-system error that is returned. For file-system error definitions, see the Guardian Procedure Errors and Messages Manual.
`filename`	is the file name in the internal format of the file that could not be accessed.

Cause DSM/SCM could not access a file because of a security violation.

Effect The activity stops in a restartable state.

Recovery Check the file-system error code in the message. For more information, including recovery actions, see the Guardian Procedure Errors and Messages Manual. Adjust the security on the file so DSM/SCM can access it and restart the activity.

5039

According to the /zzDSMSCM.Managed file, target-name manages files in the current OSS environment. target-name does not exist or does not manage OSS files. Run CLEANOSS to remove old DSM/SCM work files from the current OSS environment.

target-name

is the name of the logical target that had managed OSS files in the current OSS environment.

Cause There are several possible causes, including:

OSS management was removed for this OSS environment by DSM/SCM when this OSS environment was unavailable. In this case, event message 5325 or 5330 is generated.
DSM/SCM was initialized with INITENV when this OSS environment was not available.
The /zzDSMSCM.Managed file was placed in the root directory by something other than DSM/SCM. The file might have originated from a different OSS environment and reached the current OSS environment by copying files, backup and restore, and so on.

Effect You cannot apply OSS files to the current OSS environment until these old DSM/SCM work files are removed.

Recovery Run CLEANOSS to remove the old DSM/SCM work files.

5040

DSM/SCM has detected that SYSnn TSV subvolume-name is missing from volume-name. Initialization apply for target target-name cannot proceed.

`subvolume-name`	is the name of the missing target subvolume (TSV).
`volume-name`	is the name of the volume where the TSV was expected to be located.
`target-name`	is the system name of the target where the error occurred.

Cause The specified SYSnn TSV is not present in the list of volumes you supplied.

Effect DSM/SCM does not verify the specified target but continues with the next target.

Recovery Check that the TSV is on the correct volume. Resubmit another Verify Database activity for the target.

5041

OSS file verification for target target-name will not be done because OSS is not started with the root fileset mounted.

target-name

is the name of the logical target that manages OSS files.

Cause OSS is not started with the root fileset mounted.

Effect No OSS file verification is performed.

Recovery Start OSS and mount the root fileset.

5042

OSS file verification for logical target target-name will not be done because that OSS environment is not available(different $SYSTEM disk).

target-name

is the name of the logical target that manages OSS files.

Cause The OSS environment associated with this logical target is not running. Only the OSS environment associated with the current $SYSTEM can be started. This logical target does not manage the current $SYSTEM volume.

Effect No OSS file verification is performed for this logical target.

Recovery To verify OSS files for this logical target, system load from a SYSnn on the $SYSTEM volume managed by this logical target.

5043

target-name is supposed to manage files in the current OSS environment. According to /zzDSMSCM.Managed, oss-target is managing files in the current OSS environment. OSS file verification for target-name will not be done.

`target-name`	is the name of the logical target that manages OSS files according to the DSM/SCM target database.
`oss-target`	is the name of the logical target that manages OSS files according to the /zzDSMSCM.Managed file.

Cause There are several possible causes, including:

The OSS environment is shared between two different logical targets, and both are trying to manage the same OSS environment.
The /zzDSMSCM.Managed file was placed in the root directory by something other than DSM/SCM. The file might have originated from a different OSS environment and reached the current OSS environment by copying files, backup and restore, and so on.

Effect No OSS file verification is performed for either logical target.

Recovery Depends on which logical target is supposed to manage OSS files in the current OSS environment. If target-name, run CLEANOSS to remove the old DSM/SCM work files from the current OSS environment. The next Apply for target-name that manages OSS files will add all DSM/SCM work files for target-name. Clear the Manage OSS Files check box for oss-target if it is checked.

If oss-target is supposed to manage OSS files in this OSS environment, clear the Manage OSS Files check box for target-name. The next Apply for target-name removes OSS management from target-name.

5044

The current OSS environment is managed by target oss-target (according to /zzDSMSCM.Managed). target-name manages OSS files but is not associated with the current $SYSTEM volume. No OSS file verification will be done for target-name.

`oss-target`	is the name of the logical target that manages OSS files according to the /zzDSMSCM.Managed file.
`target-name`	is the name of the logical target that manages OSS files according to the DSM/SCM target database.

Cause The OSS environment for this logical target is not running. A different OSS environment is running.

Effect No OSS file verification is performed for logical target target-name.

Recovery To verify OSS files for this logical target, you must system load from a SYSnn on the $SYSTEM volume that is managed by this logical target.

5046

OSS file management is being removed from target target-name. The current OSS environment is not associated with any logical target.

target-name

is the name of the logical target that manages OSS files according to the DSM/SCM target database.

Cause The /zzDSMSCM.Managed file was removed from the OSS environment for this logical target.

Effect OSS file management is removed for this logical target from the target database and OSS environment. Only DSM/SCM work files are removed from the OSS environment. DSM/SCM work files are all files that have a .dsmscm prefix and all /zzDSMSCM.Managed files.

Recovery Informational message; no corrective action is necessary. The next Apply that manages OSS files restores DSM/SCM OSS file management.

5047

Verify Database has created number new zzDSMSCM.Managed file(s) that were missing in the current OSS environment.

number

is the number of zzDSMSCM.Managed files created.

Cause There should be a zzDSMSCM.Managed file in every directory that DSM/SCM manages. A verify database discovered some missing.

Effect New zzDSMSCM.Managed files are created.

Recovery Informational message only; no corrective action is needed.

5048

DSM/SCM has detected that OSS file filename has been removed, or replaced with a different version. The DSM/SCM database will be updated accordingly.

filename

is the name of the OSS file that is missing or changed.

Cause A target OSS file managed by DSM/SCM was removed or replaced with a different version from its expected directory, or a target OSS directory was removed.

Effect The DSM/SCM database is updated to reflect that the file is missing or changed.

Recovery Informational message; no corrective action is needed. A subsequent Apply ensures that all files are restored.

5050

DSM/SCM operator instruction: instruction-text.

instruction-text

is the operator instruction.

Cause The operator is required to perform a task to activate the software just applied. This informational message contains an instruction to be performed by the operator to complete the Apply or Backout activity.

Effect This message is sent with an operator instruction.

Recovery The operator should perform the specified task.

5055

TSV volume primary-volume-name alternate-volume-name not online. Apply request cannot proceed. Correct error, RESTART the activity.

`primary-volume-name`	is the name of the primary target subvolume (TSV) volume.
`alternate-volume-name`	is the name of the alternate TSV volume.

Cause The Apply activity to the specified TSV stopped because the volume was not online.

Effect The Apply activity stops in a restartable state.

Recovery Check that the volume is online; then restart the Apply activity.

5065

TSV subvolume-name on volume volume-name cannot be shared with target-name. Apply cannot proceed. Inform Planner of error.

`subvolume-name`	is the name of the target subvolume (TSV).
`volume-name`	is the name of the volume containing the TSV.
`target-name`	is the system name of the logical target that is already using the specified TSV.

Cause An Apply activity finished with errors because the planner indicated that a configuration had a TSV on a volume another target was already using. DSM/SCM does not let targets share the same TSV.

Effect The Apply activity finishes with errors.

Recovery Inform the planner of the error. After the planner corrects the error by specifying a different volume for the TSV and rebuilding the configuration, start a new Apply activity.

5070

DSM/SCM has detected that TSV subvolume-name move-action from target-volume-name free-text destination-volume-name. The DSM/SCM database will be updated accordingly.

subvolume-name

is the name of the target subvolume (TSV) that was moved.

move-action

is the situation that caused the TSV location change to be reported. Possible values and their meanings are:

Value	Description
COPIED	A COPY operation occurred.
MISSING	The TSV is missing.
MOVED	A MOVE operation occurred.

target-volume-name

is the name of the previous volume where the TSV was located (if the value of move-action is COPIED or MOVED) or the name of the volume where the TSV was expected to be located (if the value of move-action is MISSING).

free-text

displays the value TO if the value of move-action is COPIED or MOVED. If the value of move-action is MISSING, this value is null.

destination-volume-name

is the name of the new volume where the TSV is located (if the value of move-action is COPIED or MOVED) or null (if the value of move-action is MISSING).

Cause A TSV changed location.

Effect This message informs the operator and planner of the location change. The DSM/SCM database is updated to reflect the new TSV file location.

Recovery Informational message only; no corrective action is needed.

5075

DSM/SCM has detected that TSV file filename has been removed, or replaced with a different version, from expected subvolume subvolume-name. The DSM/SCM database will be updated accordingly.

`filename`	is the name of the file that has been removed.
`subvolume-name`	is the name of the expected subvolume location.

Cause A target file managed by DSM/SCM has been removed or replaced with a different version from its expected volume and subvolume location.

Effect This message informs the operator and planner of the removal. The DSM/SCM database is updated to reflect the new target subvolume (TSV) file location.

Recovery Informational message only; no corrective action is needed.

5080

No file placement performed; SAFEGUARD must be running before this APPLY or BACKOUT activity can be RESTARTED. Either a) bring up SAFEGUARD and restart the activity or b) cancel this activity and use the MI as follows before starting a new activity--use the host MI (if you performed an APPLY) or the target MI (if you performed a BACKOUT) to change the attribute for this target so that SAFEGUARD protection is no longer required.

Cause The target system is protected by Safeguard, but Safeguard was not running. No file placement can be performed at the target until Safeguard is running.

Effect The activity stops in a restartable state. No file placement is performed.

Recovery Either start Safeguard on the target system so that Safeguard can put the correct protection on the DSM/SCM files, or use the Maintenance Interface to change the system profile for the target system so that Safeguard protection is no longer required.

5085

DSM/SCM cannot continue processing your request. Two disk volumes may not have the same primary and alternate name pair primary-volume-name alternate-volume-name. Ensure that you have labelled the disks correctly.

`primary-volume-name`	is the name of the primary volume that is being shared.
`alternate-volume-name`	is the name of the alternate volume that is being shared.

Cause DSM/SCM cannot be used with systems where two or more disk volumes have the same primary volume name and alternate volume name pair.

Effect The activity completes with errors. DSM/SCM cannot process this request. DSM/SCM cannot use these volumes as destinations. The volumes can exist on this system if not used by DSM/SCM.

Recovery If you want DSM/SCM to use these disk volumes for its activities, contact your system manager. If directed, use the Peripheral Utility Program (PUP) or SCF to change the label on one of the volumes.

5090

File filename with fingerprint fingerprint does not exist at target on TSV tsv-name.

`filename`	is the name of the missing file.
`fingerprint`	is the file fingerprint of the file that is missing. A file fingerprint is a calculated checksum that uniquely identifies the file.
`tsv-name`	is the name of the subvolume where the file is missing.

Cause The file with the specified fingerprint is missing from the target.

Effect The activity finishes with errors.

Recovery The planner or operator should:

Take a system snapshot of the target system.
Input the system snapshot at the host.
Start a new Build activity on the host using the updated snapshot information.
Start a new Apply activity on the target using the updated snapshot information.

5095

Bad file-type file filename on medium.

file-type

is the file type of the file. Possible values:

Activation Package

Archive File

Configuration Information File

FAB File

Map File

Process

PURGME File

Report File(s)

RLSEID File

System Snapshot

Software Input

SYSGEN Input Product File

SYSGEN Output File

Target File

Tool File

Trace

ZPHIFI File

ZPHI6030 File

ZPHISYS File

ZSSLIST File

filename

is the file name in the internal format of the file.

medium

is the type of medium where the file is located. Possible values:

disk

tape

Cause The specified file was corrupt.

Effect The activity stops in a restartable state.

Recovery Verify that the file was created by DSM/SCM and has not been moved or modified outside DSM/SCM. If the cause of the error cannot be detected, save the file, cancel the activity, contact your service provider, and provide all relevant information:

Descriptions of the problem and accompanying symptoms
A copy of the file that caused the error
Details from the message or messages generated
Supporting documentation such as the $ZPHI Event Management Service (EMS) logs and trace files (if requested by your service provider)

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.

5100

Incomplete AP from subvolume-name on medium.

subvolume-name

is the name of the subvolume where the incomplete activation package (AP) is located.

medium

is the medium where the incomplete activation package is located. Possible values:

disk

tape

Cause An activation package was incomplete.

Effect DSM/SCM completes the activity with errors.

Recovery If files have been moved from the activation package location, restore the files back to the specified location and start the activity again. If the cause of the error cannot be detected, save the activation package files, contact your service provider, and provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as the $ZPHI Event Management Service (EMS) logs and trace files (if requested by your service provider)

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.

5110

An unmanaged file has been successfully renamed old-filename to new-filename.

`old-filename`	is the previous file name in the internal format of the file.
`new-filename`	is the new file name in the internal format of the file.

Cause A new file managed by DSM/SCM had the same name as an existing unmanaged file. The unmanaged file was renamed into the PURGEME subvolume.

Effect DSM/SCM renames the file, issues this informational message, and continues processing.

Recovery If the file is no longer needed, purge the file from the PURGEME subvolume. If the file is needed, place it in the location you want (preferably a subvolume that is not usually managed by DSM/SCM), or put it under DSM/SCM management as part of an input.

5115

Cannot continue DSM/SCM APPLY because SYSnn has changed before APPLY has completed.

Cause A change in the currently active SYSnn occurred while processing an Apply activity.

Effect The Apply activity stops in a restartable state.

Recovery Perform a system load using the SYSnn that was up while the Apply activity was in progress, and restart the activity.

5120

Failed to build TACLSEGF for new SYSnn SYSsysnn-num, coldload TACL will attempt to build TACLSEGF on coldload.

sysnn-num

is the SYSnn number of the new system.

Cause TACL failed to build the TACLSEGF file on the new SYSnn. This error is usually the result of a migration situation.

Effect The new TACLSEGF file is for a different RVU than that of the currently running system.

Recovery If you perform a system load, TACL attempts to build the TACLSEGF file. After a system load, check that the TACLSEGF file was built without errors. If the system load TACL reports an error, contact your service provider and provide all relevant information:

Descriptions of the problem and accompanying symptoms
A copy of the file that caused the error (SYSnn.ZSEGFILE)
Details from the message or messages generated
Supporting documentation such as the $ZPHI Event Management Service (EMS) logs and trace files (if requested by your service provider)

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.

5125

Failed to build TACLSEGF for current SYSnn SYSsysnn-num.

sysnn-num

is the SYSnn number of the current system.

Cause An error occurred during the Build of a TACLSEGF file on the currently running SYSnn.

Effect The activity stops in a nonrestartable state.

Recovery Contact your service provider and provide all relevant information:

Descriptions of the problem and accompanying symptoms
A copy of the file that caused the error (SYSnn.ZSEGFILE)
Details from the message or messages generated
Supporting documentation such as the $ZPHI Event Management Service (EMS) logs and trace files (if requested by your service provider)

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.

If you need to process additional requests, you can cancel the activity and start a new Apply activity. After the problem is diagnosed, delete the nonrestartable request through the Maintenance Interface.

5130

Volume pair primary-volume-name alternate-volume-name. Cannot action-name file filename on subvol subvolume-name.

primary-volume-name

is the name of the primary volume.

alternate-volume-name

is the name of the alternate volume.

action-name

is the name of the procedure or action that was in progress when the file error occurred. Possible values:

AWAITIO	OPEN
CLOSE	POSITION
CONTROL	PUP Listlabel
CREATE	READ
DELETE	READUPDATE
DEVICEINFO2	RENAME
DISKINFO	REPLY
DSC SPI command CONFIG	Safeguard access check
DSC SPI command LISTDEV	Safeguard command ADD FILE
EDITREAD	Safeguard command DELETE FILE
EDITREADINIT	SETMODE
FILEINFO	STOP
FILEINQUIRE	TAPEMOUNT
FUP Dup	UNLOCK
NEWPROCESS	WRITE
NEXTFILENAME	WRITEREAD

filename

is the file name.

subvolume-name

is the name of the subvolume.

Cause An action could not be performed on a file on the specified volume because the volume was not online.

Effect The activity stops in a restartable state.

Recovery Bring the specified volume online and restart the activity.

5135

Change in target system environment detected.

Cause One or more files have been modified since DSM/SCM placed them on the target system.

Effect The requested activity finishes nonrestartable.

Recovery Cancel the current request; then:

Use the Target Interface to perform a Verify Database request.
Use the Target Interface to perform an Independent Snapshot request.
Use the Planner Interface to rebuild and apply the last configuration.

5140

Error sfg-error deleting SAFEGUARD security attributes for filename. Change the SAFEGUARD security attributes on the file. RESTART the activity.

`sfg-error`	is the Subsystem Programmatic Interface (SPI) error that occurred on a command to the Safeguard subsystem. For Safeguard SPI error definitions, see the Safeguard Management Programming Manual.
`filename`	is the file name in the internal format of the file where the error occurred.

Cause A Safeguard SPI error occurred while deleting Safeguard security attributes for the specified file.

Effect The activity stops in a restartable state.

Recovery Check the error code in the message. For a definition and recovery action for the specified error, see the Safeguard Management Programming Manual. Secure the file under Safeguard so that DSM/SCM can delete the file’s Safeguard attributes. Restart the activity.

5145

DSM/SCM has detected an inconsistency between the database and the system. Apply request cannot proceed. Perform the following recover action: recovery-action

recovery-action

lists the steps needed to correct the problem. These steps include one or more of:

Cancel Apply request.
Perform database verify.
Create system snapshot.
Resubmit Apply request.
Perform Receive snapshot at host.
Perform Build/Apply.

Cause Files or target subvolumes (TSVs) have been moved or modified outside DSM/SCM.

Effect The activity finishes with errors. DSM/SCM does not apply the activation package.

Recovery Perform the steps listed in the message.

5150

Managed TSV tsvname has become obsolete. Cannot delete files from the TSV because SYSnn associated with the configuration being obsoleted is currently executing. Delete files from the TSV manually once the SYSnn is no longer in use.

tsvname

is the name of the obsolete target subvolume (TSV).

Cause DSM/SCM could not delete the files in the specified TSV because the associated SYSnn is in use.

Effect The activity finishes with warnings.

Recovery Delete files from the specified TSV manually once the SYSnn is no longer in use.

5151

Managed TSV tsvname has become obsolete. DSM/SCM is no longer managing this TSV. Delete files from this TSV manually once this TSV is no longer needed.

tsvname

is the name of the obsolete target subvolume (TSV).

Cause The last two configurations (the new configuration being placed and the previous configuration) share the same SYSnn. The (now obsolete) configuration prior to them went to a different SYSnn.

Effect This is an informational message. DSM/SCM does not purge obsolete TSVs in this situation because they could be useful as backups. However, DSM/SCM will no longer manage these TSVs.

Recovery When the SYSnn of the old configuration is no longer needed, delete the TSV manually. The configuration files in these TSVs are kept. The DSM/SCM files (ZFBccncc, ZPHI6030, ZMPccncc, ZPHIFI, and so on) are removed from the TSV. This does not affect the success of the Apply for the new configuration.

To have the obsolete TSVs purged automatically, before the Apply, enter:

> PATHCOM =ALTER TA-001,param DELETE-OBSOLETE-TSVS

5152

Managed OSS directory tdl-name has become obsolete. Cannot delete files from the directory beause the SYSnn associated with the configuration being obsoleted is currently executing. Remove files from this directory once the SYSnn is no longer in use.

tdl-name

is the name of the obsolete directory.

Cause DSM/SCM could not delete the files in the specified directory because the associated SYSnn is in use.

Effect The activity completes with warnings.

Recovery Manually remove files from the specified directory once the SYSnn is no longer in use.

5153

Managed TDL tdlname has become obsolete. DSM/SCM is no longer managing this directory. Remove files from this directory manually once they are no longer needed.

tdlname

is the name of the obsolete OSS directory.

Effect This is an informational message. DSM/SCM does not purge obsolete OSS directories in this situation because they could be useful as backups. However, DSM/SCM will no longer manage these OSS directories.

Recovery When the SYSnn of the old configuration is no longer needed, delete the TSV manually. The configuration files in these TDLs are kept. The DSM/SCM files (.dsmscm.* and zzDSMSCM.Managed) are removed from the TDL. This does not affect the success of the Apply for the new configuration.

To have the obsolete TDLs purged automatically, before the Apply, enter:

> PATHCOM =ALTER TA-001,param DELETE-OBSOLETE-TSVS

5160

Error file-error encountered on deleting an obsolete managed file filename. Delete the specified file manually.

`file-error`	is the number of the file-system error.
`filename`	is the name of the obsolete file.

Cause DSM/SCM could not delete the obsolete file because of the indicated file-system error.

Effect The activity finishes with warnings.

Recovery Delete the specified file manually.

5161

Error file-error encountered attempting to remove obsolete managed OSS file filename. Remove the specified file manually.

`file-error`	is the OSS file-system error that occurred. For OSS file-system error definitions, see the Open System Services System Calls Reference Manual.
`filename`	is the name of the OSS file that could not be removed.

Cause DSM/SCM could not delete the obsolete file because of the indicated error.

Effect The activity finishes with warnings.

Recovery Remove the specified file manually.

5170

DSM/SCM has detected that TSV source-volume.source-subvolume has been moved to destination-volume.destination-subvolume. destination-subvolume is not a valid SYSnn name. Verification for target target-name skipped.

`source-volume`	is the name of the source volume of the TSV.
`source-subvolume`	is the name of the source subvolume of the TSV.
`destination-volume`	is the name of the destination volume of the TSV.
`destination-subvolume`	is the name of the destination subvolume of the TSV.
`target-name`	is the name of the logical target being verified.

Cause The SYSnn was moved or renamed to a subvolume not of the format SYSnn.

Effect DSM/SCM skips verification of the logical target.

Recovery Use FUP to rename the SYSnn to the correct format.

5171

Public DLL TSV from-vol-name.subvol-name has been moved or copied to to-vol-name.subvol-name. The new subvolume name does not conform to the ZDLLrrr[a] naming convention. DSM/SCM will no longer manage this subvolume.

`from-vol-name`.`subvol-name`	is the name of the volume and subvolume where the public DLL was moved from.
`to-vol-name`.`subvol-name`	is the name of the volume and subvolume where the public DLL was moved to.

Cause A public DLL target subvolume (TSV) was moved or copied to a subvolume whose name does not conform to the ZDLLrrr[a] naming convention.

Effect DSM/SCM removes the DSM/SCM work files from this subvolume. The Verify DB completes with warnings. The ZREGPTR file is not updated to point to the new subvolume.

Recovery Check that the ZREGPTR file in the SYSnn subvolume points to a valid set of public dynamic-link libraries (DLLs). Rename the subvolume to conform to the ZDLLrrr[a] naming convention. DSM/SCM adopts the ZDLLrrr[a] TSV on the next Apply if the rrr matches the configuration revision that built the public DLLs, and all the public DLL files in the subvolume are correct.

5180

WARNING: DSM/SCM has detected that TSV source-volume.source-subvolume has been moved to destination-volume.destination-subvolume. destination-subvolume is not bootable because SYSnn-number is not an octal number.

`source-volume`	is the name of the source volume of the TSV.
`source-subvolume`	is the name of the source subvolume of the TSV.
`destination-volume`	is the name of the destination volume of the TSV.
`destination-subvolume`	is the name of the destination subvolume of the TSV.
`SYSnn-number`	is the new SYS`nn` number.

Cause The SYSnn subvolume was moved or renamed, but the nn portion of the new SYSnn is not a valid octal number.

Effect The activity completes with warnings.

Recovery Rename the SYSnn to specify a valid octal number.

5190

The SYSnn subvolume-name for the current configuration of target target-name is missing from system-volume and was not found anywhere else on the system. The target target-name is being deleted from the target system. The DSM/SCM database will be updated accordingly.

`subvolume-name`	is the name of the SYS`nn` subvolume related to the current configuration.
`target-name`	is the name of the logical target.
`system-volume`	is the name of the system volume where the SYS`nn` subvolume was expected to reside.

Cause The physical system volume was lost, or the specified logical target was deleted.

Effect DSM/SCM deletes the logical target from the target system.

Recovery If you are deleting a logical target, this is an informational message only; no corrective action is needed.

If the logical target was unintentionally deleted, perform another Build/Apply request for the same configuration.

If the message is caused by a corrupted disk, install a new disk with the same name as the old disk; then perform another Build/Apply request for the same configuration.

5200

The SYSnn subvolume-name for the previous configuration of target target-name is missing from system-volume and was not found anywhere else on the system. Backout will not be allowed. The DSM/SCM database will be updated accordingly.

`subvolume-name`	is the name of the SYS`nn` subvolume related to the previous configuration.
`target-name`	is the name of the logical target.
`system-volume`	is the name of the system volume where the SYS`nn` subvolume was expected to reside.

Cause The physical system volume was lost, or the specified logical target was deleted.

Effect DSM/SCM deletes the previous configuration. Therefore, no configuration exists for you to back out to.

Recovery Informational message only; no corrective action is needed.

5210

DSM/SCM has detected that TSV source-volume.source-subvolume has been moved to destination-volume.destination-subvolume for target target-name. The DSM/SCM database will be updated accordingly.

`source-volume.source-subvolume`	is the name of the source volume and subvolume of the target subvolume (TSV).
`destination-volume.destination-subvolume`	is the name of the destination volume and SYS`nn` subvolume of the TSV.
`target-name`	is the name of the target system.

Cause A SYSnn subvolume was manually moved.

Effect DSM/SCM issues this message.

Recovery Informational message only; no corrective action is needed.

5220

DSM/SCM has detected that the SYSnn and CSSnn were not moved to the same volume and nn number. SYSnn: SYSnn-volume.SYSnn-subvolume CSSnn: CSSnn-volume. CSSnn-subvolume. Verification for target target-name skipped.

`SYSnn-volume`	is the name of the SYS`nn` volume.
`SYSnn-subvolume`	is the name of the SYS`nn` subvolume.
`CSSnn-volume`	is the name of the CSSnn volume.
`CSSnn-subvolume`	is the name of the CSSnn subvolume.
`target-name`	is the name of the logical target being verified.

Cause The associated SYSnn and CSSnn subvolumes were placed on different volumes or have a different nn.

Effect DSM/SCM skips verification of the logical target.

Recovery Check that the associated SYSnn and CSSnn subvolumes are on the same volume. Check the timestamps of the ZPHIFI files in the various SYSnn and CSSnn subvolumes on the system. The timestamps indicate which CSSnn goes with which SYSnn. Once you determine this, rename the subvolumes so that the CSSnn and the SYSnn are correctly paired. Now the Verify Database should finish, and you can restart the Apply.

5221

TSV first-vol-name.subvol-name and second-vol-name.subvol-name are required to be on the same volume. Verification for target target-name skipped.

`first`-`vol-name.subvol-name`	is the name of the volume and subvolume where the first TSV is located. Example: $SYSTEM.SYS00
`second`-`vol-name.subvol-name`	is the name of the volume and subvolume where the second TSV is located. Example: $DATA.ZDLL005
`target-name`	is the name of the logical target being verified.

Cause Two TSVs that are required to be on the same volume, usually $SYSTEM, have been found on different volumes.

Effect DSM/SCM skips verification of this logical target, and the Verify DB completes with warnings.

Recovery Move the TSVs to the same volume and run Verify DB again.

5222

Unable to update DSM/SCM-file to point to the location of moved Public DLL TSV dll-subvolume. Modify the dsv-location-file file to point to the new Public DLL location.

`DSM/SCM-file`	is the name of the ZREGPTR/XREGPTR file that Verify Database activity was trying to update.
`dll-subvolume`	is the name of the DLL subvolume in ZDLL`rrr`[`a`] format.
`dsv-location-file`	is either ZREGPTR or XREGPTR. A file that has the location of Public DLL in ZDLL`rrr`[`a`] format.

Cause Verify Database encountered an error while updating the ZREGPTR or XREGPTR file with the new location of the moved Public DLL TSV.

Effect The activity finished with warnings.

Recovery Manually modify the ZREGPTR or XREGPTR file to the new public DLL location.

5230

WARNING: File filename is incorrect or missing and needs to be placed. The correct files is not available from the activation package/archive. The correct file is available on the target system in another location. The ‘Place all files using host files’ or ‘Place files that have changed using host files’ option has been seleted. A target file is being used anyway to allow the apply to continue. Further messages of this type will be suppressed.Continuing.

filename

is the name of the file that needs to be placed on the target system.

Cause The last snapshot on the host system does not match the target system. The file cannot be accessed from the host.

Effect The Apply completes with warnings. The required files that could not be accessed from the host were copied from one target subvolume to another.

Recovery Perform a backout if all or changed files must be copied from the host. The backout sends a snapshot to the host. When the Apply is reinitiated, the snapshot will match the target system, and this error should not appear.

5240

Previous error encountered while attempting to recreate missing file-type. Not critical to the success of the Apply. Continuing.

file-type

is the file type of the file. Possible values:

ZPHIFI File

ZSSLIST File

ZPHI6030 File

Cause The error in the previous message occurred when DSM/SCM attempted to re-create the missing file.

Effect The Apply continues. If you run Verify Database and ZPHI6030 files are missing, these target subvolumes are removed from the target database.

Recovery No action is required. However, to prevent future errors of this kind, refer back to the previous EMS message and determine why the files needed were missing and why the re-creation of the file failed. You can restore the files from backup.

5250

ASSIGN assign-filename has an invalid value of actual-filename. Correct the assign value in the Pathway server class. RESTART the activity.

`assign-filename`	is the name assigned to the actual file.
`actual-filename`	is the ASSIGN value. This file name is the actual file.

Cause A file name was expected as the ASSIGN value. The subvolume or file name portion is missing.

Effect The activity stops in a restartable state.

Recovery Correct the ASSIGN value through the Pathway server. For example:

> PATHCOM $YPHI
> ALTER ta-001, ASSIGN FILEMGR, $SYSTEM.CUSTOM.FILEMGR

If you do not want the file specified in the ASSIGN to be used, cancel the request, delete the ASSIGN, and restart the activity:

> ALTER ta-001, DELETE ASSIGN FILEMGR

5260

ASSIGN assign-filename, assign-value, is being used.

`assign-filename`	is the name assigned to the actual file.
`assign-value`	is the ASSIGN value. This file name is the actual file.

Cause The ASSIGN is being used because it has been defined in the Pathway server class.

Effect The file specified in assign-value is used instead of the default file.

Recovery Informational message only; no corrective action is needed.

5270

File filename has an invalid alternate key filename. Correct the alternate key value for this file with FUP ALTER file-name, ALTFILE alt-file command. RESTART activity.

filename

is the file that contains an invalid alternate key file reference.

Cause DSM/SCM received error 21 from the File Utility Program (FUP) when attempting to copy (DUP) this file. The file has an incorrect alternate key attribute.

Effect The activity stops in a restartable state.

Recovery Correct the alternate key file name referenced in the specified file and restart the activity.

5280

WARNING: Insufficient information to process the Place All Files option. The Place All Files option has been disabled. The normal default behavior of placing only changed files will be enabled. The current and previous configuration must be applied on the system by an T6031AAO or later before the Place All Files option can be used.

Cause The Place All Files option could not be used because no historical information was in the database. The DSM/SCM version used to apply the current or previous configuration is prior to T6031AAO. This historical information in the database was not produced until T6031AAO. For more information on the Place All Files option, see the DSM/SCM User’s Guide.

Effect The Apply completes with warnings. Only changed files are placed.

Recovery Informational message only; no corrective action is needed. The Place All Files option works with future applied configurations as long as the next two configurations are not backed out.

5300

The target SYSNN volume primary-volume alternate-volume is not up as $SYSTEM. The target SYSNN volume must be the coldload volume because OSS files are being installed. CANCEL the Apply. Coldload from the target SYSNN volume and RESTART the Apply.

`primary-volume`	is the volume primary name for the target SYS`nn`.
`alternate-volume`	is the volume alternate name for the target SYS`nn`.

Cause The target SYSnn is not up as $SYSTEM.

Effect The activity stops in a restartable state.

Recovery Cancel the Apply. System load from the target SYSnn volume and restart the Apply.

5305

The current OSS environment is managed by target oss-system (according to /zzDSMSCM.Managed). To switch OSS management from oss-system to target-system, CANCEL the Apply, run CLEANOSS, run Verify Database, then RESTART the Apply.

`oss-system`	is the name of the logical target that manages OSS files according to the /zzDSMSCM.Managed file.
`target-system`	is the name of the logical target attempting to manage OSS files in the current OSS environment.

Cause According to the /zzDSMSCM.Managed file, the current OSS environment is being managed by a logical target other than the one trying to manage OSS files with the current Apply.

Effect The activity stops in a restartable state.

Recovery If you want target-system to manage OSS files in the current OSS environment, cancel the Apply, run CLEANOSS, and use verify database to remove OSS management of the current OSS environment by oss-system. Restart the Apply.

If you do not want target-system to manage OSS files, cancel the Apply, clear the Manage OSS Files check box for this target, and perform another Build/Apply.

5310

The current OSS environment contains old DSM/SCM work files. Run CLEANOSS to remove all DSM/SCM work files from this OSS environment. RESTART the activity.

Cause An unexpected /zzDSMSCM.Managed file was found in the OSS environment, and no other logical targets manage this OSS environment.

Effect The activity stops in a restartable state.

Recovery Run CLEANOSS to remove the old DSM/SCM work files (dsmscm.* and zzDSMSCM.Managed files) from the OSS environment, run Verify Database to clear OSS management from the target database and then restart the Apply.

5320

Missing /zzDSMSCM.Managed file. CANCEL Apply. Run CLEANOSS, then Verify Database to remove prior OSS file management for Logical Target target-name. Then start Apply. Management of OSS files will be restored.

target-name

is the name of the logical target that OSS files are being installed for.

Cause The /zzDSMSCM.Managed file was removed.

Effect The activity stops in a restartable state.

Recovery Cancel the Apply. Run CLEANOSS and then run verify database to remove OSS management for this logical target. Restart the Apply to add management of OSS files back to the logical target.

5321

OSS management cleanup is required because of a recent Backout. CANCEL the Apply. Run CLEANOSS, then Verify Database to remove prior OSS file management for Logical Target target-name. Then start Apply. Management of OSS files will be restored.

target-name

is the name of the logical target that OSS files are being installed for.

Cause The last configuration, which managed OSS files, was backed out. The current configuration does not manage OSS files. Extra OSS management cleanup was not performed during the Backout because ZPHIRNM requires these files to be present. The new configuration being applied manages OSS files.

Effect The activity stops. A Verify Database must perform OSS management cleanup before the Apply can continue.

Recovery Cancel the Apply. Run CLEANOSS and Verify Database to remove OSS management of the current OSS environment, then restart the Apply.

5325

Management of OSS files will be removed from Target target-name. Removal of DSM/SCM work files cannot be done because OSS is not started with root fileset mounted. Start OSS and run CLEANOSS to remove these files.

target-name

is the name of the logical target on which OSS file management will be removed.

Cause OSS is not started with the root fileset mounted.

Effect The activity completes with warnings. OSS management is removed from the logical target, and the target database is updated. DSM/SCM work files are not removed from the OSS environment. If an Apply tries to install OSS files in this OSS environment with the old DSM/SCM work files still present, the Apply sends event message 5039.

Recovery Run CLEANOSS when the OSS environment becomes available.

5330

Management of OSS files will be removed from the target target-name. DSM/SCM OSS work files will not be removed because the /OSS environment for this target is not available. Run CLEANOSS to remove these files when this OSS environment becomes available.

target-name

is the name of the logical target on which OSS file management will be removed.

Cause The OSS environment is not available because a different $SYSTEM volume was system loaded.

Effect The Apply completes with warnings. OSS management is removed from the logical target, and the target database is updated. DSM/SCM work files are not removed from the OSS environment. If an Apply tries to install OSS files in this OSS environment with the old DSM/SCM work files still present, the Apply sends event message 5039.

Recovery System load from a SYSnn on the $SYSTEM volume associated with the OSS environment, then run CLEANOSS when the OSS environment becomes available.

5331

Management of OSS files will be removed from the target target-name. DSM/SCM OSS work files will not be removed because the /zzDSMSCM.Managed file indicates that target oss-system is managing the OSS environment. Run CLEANOSS to remove these files if target oss-system is not managing the OSS environment.

`target-name`	is the name of the logical target on which OSS file management will be removed.
`oss-system`	is the name of the logical target that is actually managing this OSS environment.

Cause The /zzDSMSCM.Managed file indicates that a different logical target is managing this OSS environment.

Effect The Apply completes with warnings. OSS management is removed from the logical target, and the target database is updated. DSM/SCM work files are not removed from the OSS environment.

Recovery If the OSS environment is managed by oss-system, no action is required. Otherwise, run CLEANOSS.

5335

Management of OSS files has been removed for target target-name.

target-name

is the name of the logical target for which OSS file management was removed.

Cause The Manage OSS Files check box was cleared for this logical target before this Build/Apply request. The previous Build/Apply for this logical target managed OSS files.

Effect All DSM/SCM work files (.dsmscm.* and zzDSMSCM.Managed files) used to manage OSS files are removed. All other OSS files are left in place. All records regarding OSS management for this logical target are removed from the DSM/SCM target database.

Recovery Informational message only; no corrective action is needed.

5340

Warning: $SYSTEM.SYSnn.dll-dsv-location-file will not be changed to point to the public DLLs for the new configuration in dll-subvolume because OVERRIDE-SYSNN has been specified.

SYS`nn`	is the currently executing SYS`nn` subvolume.
`dll-subvolume`	is the TSV where the new set of public DLLs are placed.
`dll-dsv-location-file`	is the name of the ZREGPTR/XREGPTR file having the location of Public DLL in ZDLL`rrr`[`a`] format

Cause A new set of public dynamic-link libraries (DLLs) were placed in a new DLLrrr[a] target subvolume (TSV), but the ZREGPTR/XREGPTR in the running SYSnn subvolume was not changed because OVERRIDE-SYSNN was specified.

Effect A new set of public DLL files are placed in the specified subvolume as a backup. The ZREGPTR/XREGPTR file is not changed to point to these new public DLLs. The Apply continues but completes with warnings. OVERRIDE-SYSNN might prevent matching NonStop operating system files from being placed in the SYSnn subvolume. In that case, the new set of public DLLs might not function correctly with the existing operating system files in the SYSnn subvolume.

Recovery None. Informational message. You can try the new set of public DLLs if you have problems with the public DLLs in use.

5350

A coldload will be required to activate the public DLLs in this new configuration because the active DLLs are not correct. A correct set of public DLLs will be placed in $SYSTEM.correct-dll-subvolume. The set of public DLLs has not changed from configuration-name. The active set of public DLLs in active-dll-subvolume is incorrect because dll-file is reason. No other correct dll-subvolume-template [a] TSVs were found.

correct-dll-subvolume

is the target subvolume (TSV) where the correct set of public DLLs will be installed.

configuration-name

is the name of the configuration that last built the set of public DLLs. This configuration was created before the configuration was applied; for example:

\ZEUS DEFAULT 23

active-dll-subvolume

is the subvolume where the active set of public DLLs exists. An active set of public DLLs is the set used in the last system load.

dll-file

is the name of the first active public DLL file found to be incorrect.

reason

is the reason the public DLL file is incorrect, either missing or different.

dll-subvolume-template

is the ZDLLrrr subvolume name template that DSM/SCM has searched. DSM/SCM also searches subvolumes with this name and an appended alphabetic character A through Z; for example, ZDLL005. DSM/SCM has searched all subvolumes ZDLL005[a-z] for a correct set of public DLLs.

Cause The set of public dynamic-link libraries (DLLs) has not changed from the previous configuration. DSM/SCM expected to find a correct set of public DLLs already installed on the system.

Effect DSM/SCM creates a new ZDLLrrr[a] TSV. The Apply completes with warnings.

Recovery A system load is required to activate the configuration. The Planner Interface might not have indicated that a system load is required. You must perform a system load to activate the correct set of public DLLs.

5360

A coldload will be required to activate the public DLLs in this new configuration because the active DLLs are not correct. The active set of public DLLs in $SYSTEM.active-dll-subvolume is incorrect because dll-file is reason. A correct set of public DLLs were found in $SYSTEM.correct-dll-subvolume.

`active-dll-subvolume`	is the subvolume where the active set of public DLLs is located.
`dll-file`	is the name of the first active public DLL file found to be incorrect.
`reason`	indicates why the DLL file was incorrect. The value is either missing or different.
`correct-dll-subvolume`	is the ZDLL`rrr`[`a`] TSV name that contains a correct set of public DLLs.

Cause The active set of public DLLs is not correct. Another correct set of public DLLs was found on the system. Because DLLs were not built for the new configuration, the Planner Interface might not have indicated that a system load is required. This message is not sent when the OVERRIDE-SYSNN parameter is specified.

Effect The Apply completes with warnings.

Recovery Perform a system load to activate the correct set of public DLLs.

5370

Waiting for the clone Applies to complete on the following system(s): system-names. If any of these Clone Applies can not be completed, their Apply completion file, named X(system-name) in AP subvolume subvolume, must be renamed to M(system-name) in order for this master Apply to complete.

`system-names`	is a list of systems that have not yet completed the clone Apply; for example, “\XYZ02, \XYZ04”.
`subvolume`	is the location of the activation package subvolume.

Cause One or more clone Applies are not yet completed.

Effect The master Apply waits for all the clone Applies to complete, rechecking their status every five seconds. This message is sent every time the Applies on any listed systems change.

Recovery Wait for the clone Applies to complete. If a clone Apply cannot complete, you must rename its Xsystem-name Apply completion indicator file to Msystem-name in the specificed activation package subvolume.

5371

Clone Apply system-name logical-target-name completion-message.

`system-name`	is the name of the target system defined as a master.
`logical-target-name`	is the name of the logical target on `system-name`.
`completion-message`	is one of these completion status messages: Completed successfully Completed with warning(s) Completed with error(s) Was abandoned

Cause A clone Apply completed.

Effect The completion status of the clone Applies affects the master Apply request completion status as displayed in the Request Status window of the Planner Interface.

Recovery This message is informational. No recovery action is necessary.

5372

One or more clone Applies have been abandoned. AP subvolume subvolume will not be purged. Purge this subvolume when it is no longer needed.

subvolume

is the location of the activation package subvolume.

Cause One or more clone Applies is manually abandoned. The Xsystem-name files were manually renamed to Msystem-name in subvolume.

Effect subvolume is not purged so you can retry the Apply later.

Recovery Purge subvolume when you no longer need to apply it to any clone group targets.

5373

Warning: The clone group Apply completion file filename is missing. Clone group Apply status may not be complete for all the clone group target systems.

filename

is the name of the Apply completion file for the master Apply.

Cause The master Apply completion file is missing. The entire activation package subvolume might have been purged by a clone Apply performed with an earlier DSM/SCM product version.

Effect If the Apply completion file for other clone group targets is also missing, the master Apply does not report Apply status for those targets. Some clone Applies might not complete successfully.

Recovery Check the Apply status on each clone group target system. Check that all clone group systems are running a clone-capable DSM/SCM product version.

6000

Request request-name has been CANCELed.

request-name

is the name of the request that has been cancelled.

Cause A planner or operator cancelled the specified activity.

Effect The activity is cancelled.

Recovery Informational message only; no corrective action is needed.

6005

Cannot communicate with server, PATHWAY error psend-error, file system error file-error, serverclass server-class-name, PATHMON pmon-name. Correct PATHWAY error. RESTART the activity.

`psend-error`	is the Pathsend error code returned. Pathsend error codes are defined in the TS/MP Pathsend and Server Programming Manual.
`file-error`	is the file-system error that occurred (if any). For file-system error definitions, the Guardian Procedure Errors and Messages Manual.
`server-class-name`	is the name of the Pathway server class that returned the error.
`pmon-name`	is the name of the Pathway monitor (PATHMON) process that returned the error.

Cause A Pathsend error occurred.

Effect The activity stops in a restartable state.

Recovery Check the Pathsend error code in the message. For the definition and recovery action for the specified error, see the TS/MP Pathsend and Server Programming Manual. If applicable, check the file-system error code in the message. For more information about file-system errors, including recovery actions, see the Guardian Procedure Errors and Messages Manual. Correct the Pathsend error and restart the activity.

6010

Cannot cancel request-name at this node. Planner must issue a CANCEL at the local node target-name.

`request-name`	is the text of the request that was not cancelled.
`target-name`	is the system name of the local node where the request must be canceled.

Cause A DSM/SCM cancel operation could not be performed at this node because the activity to be canceled is being performed at a remote node. A DSM/SCM activity must be canceled at the local node.

Effect The activity is not canceled and continues processing.

Recovery The planner must cancel the activity at the local node.

6015

Timer error condition-code, on timer-type. RESTART activity.

condition-code

is the condition code returned from the SIGNALTIMEOUT or CANCELTIMEOUT procedure calls. Possible values:

Value	Description
0	Cannot allocate a time list element (TLE)
1	Successful
2	The timeout value is illegal. This can occur when you schedule a request more than 248 days in the future.

timer-type

is the timer where the error occurred. Possible values:

Value	Description
Cancel	Error occurred trying to cancel a timer via the CANCELTIMEOUT procedure.
Start	Error occurred trying to start a timer via the SIGNALTIMEOUT procedure.

Cause An internal DSM/SCM scheduling error occurred.

Effect The activity stops in a restartable state.

Recovery Check the condition code in the message. For a definition of the error, see the Guardian Procedure Calls Reference Manual for the SIGNALTIMEOUT and CANCELTIMEOUT procedures. Cancel the request and change the scheduled run time. Restart the activity.

6020

request-name currently executing on target-name. Cannot start a activity-name activity at this time. Start activity-name activity after current activity has completed.

`request-name`	is the name of the request that is currently executing.
`target-name`	is the system name of the node where the request is executing.
`activity-name`	is the name of the request you are trying to submit.

Cause A second activity was requested while one activity was in progress. Only one activity can execute at one time.

Effect The second request is not started. A second activity can be performed only after the current one is completed.

Recovery Restart the activity after the current activity has completed.

6025

target-name component replied with error file-error. Planner must investigate EMS events at remote system to diagnose and fix the problem. RESTART activity.

`target-name`	is the system name of the node where the error occurred.
`file-error`	is a file-system error returned by the remote system.

Cause An error occurred at a remote system.

Effect The error must be corrected at the remote system. To the local system, this is an informational message only; no corrective action is needed.

Recovery Check the file-system error code in the message. For more detailed information about file-system errors, including recovery actions, see the Guardian Procedure Errors and Messages Manual.

7000

export-type file(s) exported to export-subvolume-name.

export-type

is the type of file that was exported. Possible values:

EMS Template

SPI Definition

Privileged Declaration

export-subvolume-name

is the name of the destination subvolume (DSV) where the files were exported.

Cause The user requested that DSM/SCM export files from the DSM/SCM archive.

Effect The request was completed. The files are on the specified subvolume.

Recovery Informational message only; no corrective action is needed.