HPS0000-HPS0099

Note

Three-digit messages are used only for ISPF functions and are displayed from within the ISPF interface to ChangeMan SSM. All three-digit messages have been removed from this Guide and can be referenced in the ChangeMan SSM Messages Guide.

`HPS0000I Job Started: 'start time',`

Job Ended : 'end time',

Warning cnt: 'nr'

Severe msgs: 'nr'

Explanation: This message appears at the end of each job.

Solution: This is an informational message that does not require any user action.

`HPS0004E Object Master append failure. RC='rc'.`

Explanation: The Object Master could not be attached to the Site Master and initialized successfully. The Object Master must be an existing VSAM data set before it can be attached.

Solution: Use the sample $INIT JCL to define an Object Master. This JCL is provided in the INSTALL data set. Refer to the ChangeMan SSM Install Guide.

`HPS0005E Set group administrator mode failed.`

`HPS0006E ChangeMan SSM GROUP does not exist.`

Solution: Contact ChangeMan SSM Technical Support.

`HPS0007E The Delta Master file could not be opened.`

Explanation: Updates to the Delta Master has failed.

Solution: Contact ChangeMan SSM Technical Support.

`HPS0008E 'DD NAME' is not a valid snapfile. RECFM must be FB and LRECL must be 'num'. Header must be valid.`

Explanation: The file referenced by the DD statement is not a valid snapfile.

Solution: Verify that the DD statement is pointing to the correct file.

`HPS0009E SET USER failure. RC='rc'.`

Explanation:

Solution: Contact ChangeMan SSM Technical Support.

`HPS0010E Object previously defined: Object 'object name'.`

Explanation: Object has already been defined.

Solution: Verify the correct object has been entered.

`HPS0011E OBJVIEW failure. RC='rc', Data set name DSN: 'dsn'.`

`HPS0012E Rejected command or Syntax error. "value" command "nr"-"nr" Col. "nr".`

Explanation: The command was either rejected as invalid or contained an invalid parameter.

Solution: Correct the command and/or parameter in error and resubmit the job.

`HPS0013E Syntax error 65. Day-of-month cannot be zero`

* Program return code = 'return code' *

`HPS0014E Memory ptrs not valid. IDVMEMLS=',IDVMEMLS, IDVMEMLA=',IDVMEMLA`

`HPS0015E No backups found for Member: "member" in Data set DSN: 'dsn'.`

Explanation: There are no backups for the member selected in specified data set.

Solution: Verify correct member and data set has been selected.

`HPS0016E 'DD NAME' open failure. R15='nr' Unable to open 'name'`

Explanation: The SYSUT1 or SYSUT2 data set cannot be opened.

Solution: Check the JCL to ensure that the DD statements are pointing to the correct DSNs.

`HPS0017E Too much list memory for Member: 'member'.`

`HPS0018E Backup RC='rc' Member: 'member' Dsn: 'dsn'.`

`HPS0018I Backup RC='rc' Member: 'member' Dsn: 'dsn'.`

`HPS0018W Backup RC='rc' Member: 'member' Dsn: 'dsn'.`

`HPS0019E Recover failed. RC='rc' Member: 'member' Dsn: 'dsn'.`

Explanation: Recover for selected member in data set specified failed.

`HPS0020E HPSPLIB DD is required. Not found: SYS1.PARMLIB`

Explanation: HPSPARMS member not found in indicated data set.

Solution: Either add member HPSPARMS to the indicated data set, or supply an HPSPLIB statement which points to the library and member name of your SSM parameters.

`HPS0021E Backup failed. Member not found: "member" DSN: 'dsn'.`

Explanation: Member selected for backup is not found.

Solution: Verify correct member and data set name is entered; resubmit.

`HPS0022E SETCON failure. RC='rc'.`

Explanation: User is not a Group Administrator.

Solution: Contact ChangeMan SSM Technical Support.

`HPS0022I PARMLIB in effect: 'parmlib'`

Security Userid: 'AUTH id'

Explanation: This message specifies the security entity under which the job is being run.

Solution: This is an informational message that does not require any user action.

`HPS0023E HPSPLIB DD member name not specified.`

Explanation: The HPSPLIB member name is missing.

Solution: Correct the error and resubmit.

`HPS0024E Open failure of PARMLIB DD 'dismantle'`

Explanation: The specified PARMLIB failed to open.

Solution: Correct the error and resubmit.

`HPS0025E PARMLIB Dsn is not fixed blocked: 'dsn'`

Explanation: The PARMLIB data set does not have the correct data set attributes. It must be fixed-blocked with an LRECL of 80. Either the data set specified in the $PARMSET job is incorrect or the HPSPLIB DD statement in your job is pointing to an incorrect data set name.

Solution: Correct the error and resubmit.

`HPS0026E * Error * Site Master 1st record is invalid. Key of record is 'Record key' and length='Record length'`

Explanation: The first record in the Site Master has an unexpected Record Type. This is an internal check to guarantee the integrity of the Site Master.

Solution: If possible, restore the integrity of the Site Master. If this cannot be done, contact ChangeMan SSM Technical Support.

`HPS0027E * Error * Site Master record length is invalid. Key of record is 'Record key' and length='Record length'`

Explanation: While reading the Site Master, an invalid record length was encountered. This may indicate an integrity problem on the Site Master.

Solution: If possible, restore the integrity of the Site Master. If this cannot be done, contact ChangeMan SSM Technical Support.

`HPS0028E * Invalid record type 'Record key' in Site Master.`

Explanation: While reading the Site Master, an invalid Record Type was encountered. This may indicate an integrity problem on the Site Master.

Solution: If possible, restore the integrity of the Site Master. If this cannot be done, contact ChangeMan SSM Technical Support.

`HPS0029I Successful open of Site Master: 'cluster name'`

Explanation: The Site Master has been opened.

Solution: This is an informational message that does not require any user action.

`HPS0030E * Error *Site Master record 'Record key' points to a non-existent OM`

Explanation: A Site Master record refers to an Object Master that does not exist. This is a Site Master integrity problem. An Object Master may have been detached from the system without using the standard procedure provided in the ChangeMan SSM's ISPF component.

Solution: If the reason cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0031E * Failure of cluster name locate * for cluster 'Cluster name'`

Explanation: The Site Master or the Object Master are not cataloged data sets. They must both be VSAM data sets.

Solution: Refer to the ChangeMan SSM Install Guide for the appropriate installation procedures.

`HPS0032E * Initialization aborted * R0 = 'content'`

Explanation: The initialization process aborted because of a volume allocation error. Register 0 contains the program Return Code.

Solution: If the reason cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0033E Vsam cluster not found in VVDS.`

Cluster name='cluster name'

Explanation: The VSAM data component was found in the VVDS (VSAM Volume Data Set) but not in the VTOC (Volume Table of Contents). It is not a legitimate VSAM data set. (The product reports any possible integrity problems observed during its functions.)

Solution: If the reason cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0034I * Site Master remains in sequential mode. *`

Explanation: The Site Master was opened for random processing. It was discovered to be a new file and then opened for sequential processing.

Solution: This is an informational message that does not require any user action.

`HPS0035E Record 0 has invalid object count 'number of tracked objects'`

Explanation: The Site Master's indication of the total number of tracked Objects in the Object Master is incorrect. This may be an integrity problem.

Solution: If possible, restore the integrity of the Site Master. If this cannot be done, contact ChangeMan SSM Technical Support.

`HPS0036I Volser = 'volser' Object = 'object name'`

Explanation: During Global Event Tracking (HPSGLOBE), the named Object was encountered and processed.

Solution: This is an informational message that does not require any user action.

`HPS0037I M-lrecl = 'size' , M-datsi = 'size' Max-lrec = 'maximum VSAM record size'`

Explanation: After a VSAM file is located in the VVDS (VSAM Volume Data Set), both the CI and Maximum Record Size are logged. This is associated with message HPS0036I when the file is VSAM.

Solution: This is an informational message that does not require any user action.

`HPS0038E Site Master requires conversion.`

Explanation: The Site Master is at a level lower than V820. It must be converted to V820 format.

Solution: Use the JCL provided in the somnode.SSM.INSTALL(SSM8CONV) member to convert the Site Master to the new format.

`HPS0039E Site Master and Object Masters are not supported. At least 'site master level' is required. Current version, 'version of the site master'`

Explanation: The level of the Site Master is not at the proper level required by the current version of the software.

Solution: Run the job to convert the Site Master and its associated Object Master.

`HPS0039I Override accepted: 'parameter'.`

Explanation: The override parameter has been accepted.

`HPS0040E PARMLIB Dsn lrecl is not 80 'dsn'`

Solution: Correct the error and resubmit.

`HPS0041E Invalid parameter “parameter”.`

Explanation: The override parameter in the JCL pointed by the //HPSPLIBO DD is invalid.

Solution: Correct the override parameter.

`HPS0041W Invalid parameter "parameter"`

Explanation: The override parameter in the JCL pointed by the //HPSPLIBO DD is invalid.

Solution: Correct the override parameter.

`HPS0042W Parameter is not unique.`

Explanation: The override parameter in the JCL is not unique.

Solution: Check the data of the //HPSPLIBO DD.

`HPS0043W Invalid numeric field specified in the override parameter.`

Explanation: The override parameter in the JCL has an invalid numeric field.

Solution: Check the data of the //HPSPLIBO DD.

`HPS0044W Invalid value in the override parameter.`

Explanation: The override parameter in the JCL contains invalid data.

Solution: Check the value.

`HPS0045E Missing required parameter: "parameter"`

Explanation: The HPSPARMS member lacks the required parameter.

Solution: Edit and save this member and resubmit the job.

`HPS0046E DD HPSIN is required.`

Explanation: The DD HPSIN is required.

Solution: Correct and resubmit the job.

`HPS0047I Object 'zFS filename'.`

`HPS0048E RTORACCHECK (not recommended) and RTORACFID are mutually exclusive parameters.`

`HPS0049I * Master Files Set to Read-Only Mode. *`

Explanation: This message may be issued for either of the follow reasons:

The current TSO UserId does not have SAF authority to update the SSM SITE or OBJECT master files.
Your environment does not have the RACF “protectall” option and there is no specific or generic profile in the DATASET class to protect the master files. RACF issues a return code of 4 and SSM handles this as an error and sets the master files to Read Only mode.

`HPS0050E RLS has prevented access to the Master files. `

The RTO must be down, all ISPF users must be signed off, and all SSM batch

jobs must have completed before starting the $INTEG job.

Change Tracking functions cannot be started while HPSINTEG is running.

`HPS0051E Unable to allocate Site Master as defined in HPSPARMS: SITEMASTER 'sitemaster-dsn'.`

`HPS0052E SSM appears to be active in another screen. Only one instance may be active per ISPF userid.`

`HPS0053E QUERY error, Return= 'Query Return Code' Reason = 'rc'.`

`HPS0054I ChangeMan SSM Site Master is in use by: 'enqueue holder'`

HPS0100-HPS0199

`HPS0100I Dynamic allocation of: 'filename'`

SVC99 error field = x'0000' info = x'0000'

Explanation: This is an informational message issued when TRACE is enabled in the $INTEG job. No action is required as the error code from the dynamic allocation is zero.

`HPS0100W FAILURE DYNAMIC ALLOCATION OF FILE`

'filename':SVC99 ERROR

FIELD = 'error code', INFO = 'reason code'

Explanation: Dynamic allocation of the specified file failed. The error code and the reason code are given in the message. Refer to the "Interpreting DYNALLOC Return Codes" section of the Authorized Assembler Services Guide, or the ISPF tutorial as follows:

Select Option Tutorial (T) from the ISPF main Menu.
Press Enter to go to the next page.
Select Table of Contents (TOC).
Select Appendix (A) for Dynamic Allocation Errors.
Select Appendix (A) for Dynamic Allocation Interface Routine (DAIR).
Press Enter to go to the next page. Use the second character in the reported error code as a class indicator. For example, error code 0210 is in class 2.
Select the class code determined above to see the detail of the message. Error code 0368, which is a common cause of SVC99 failure, indicates lost APF authorization.

Solution: Determine the cause of the failure, and resubmit the job; or reinvoke the ISPF function.

`HPS0101E FAILURE DYNAMIC ALLOCATION OF VOLUME`

'volser':SVC99 ERROR

FIELD = 'error code', INFO = 'reason code'

Explanation: Dynamic allocation of the specified volume failed. The error code and the reason code are given in the message.

Solution: Follow the instructions described in message HPS0100W.

`HPS0102T 'ACBTYPE' FILE OPENED CLUSTER, 'cluster name'`

USING MACRF = 'macro format'

Explanation: This is a trace (or logging) message. The named VSAM cluster was opened successfully.

Solution: This is a trace message. User actions will depend on the purpose of the trace.

`HPS0103E OPEN/CLOSE FAILURE ON 'ACB type'`

FILE CLUSTER = 'ACB cluster name'

MACRF = 'ACB macro format'

R15 = 'content' R0 = 'content' ERROR-CODE = 'ACB error field'

Explanation: During an OPEN or CLOSE function for the named VSAM cluster, an error occurred. The cluster name, the MACRF used to open/close the cluster, the contents of register 15 and register 0, along with the error code extracted from the ACB are all logged to identify the exact cause of the error.

Solution: Refer to the IBM DFSMS Macro Instructions for Data Sets manual, VSAM Macro Return and Reason Codes section. VSAM sets a reason code in the RPL. Reason codes are associated with a return code in register 15. For a listing of VSAM messages, see the IBM System Messages and Codes. Correct the ISPF function.

`HPS0104E HPSTRACK hh:mm:ss Key = 'key of record'`

** Get Failure ** on SM file cluster 'cluster name',

MACRF = 'macro form', RPL OPTCD = 'RPL option code',

R15 = 'content of register 15'

R0 = 'content of register 0'

FDBK = 'reason code'

* Program return code = 'return code' *

Explanation: A VSAM error occurred. The RPL return code is in register 15, and the reason code (RPLERRCD) is in the FDBK field. Refer to the IBM manual, DFSMS/MVS Macro Instructions for Data Sets, for information about interpreting these fields.

Solution: Correct the cause of the error and re-try the operation. In some cases, the integrity check program HPSINTEG will need to be run to remove any vestigial entries from the failed operation. If the cause cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0105E Open Error volser, 'volser'`

Explanation: An SVC 22, issued to open the VTOC (Volume Table of Contents) of the specified volume, failed.

Solution: If the reason cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0106E OBTAIN ERROR VOLSER = 'volser' R15 = 'content'`

Explanation: An Obtain request for a DSCB4 record in the VTOC (Volume Table of Contents) failed. The return code from the Obtain function is in register 15.

Solution: Contact ChangeMan SSM Technical Support.

`HPS0107W * I/O read failure on volume 'volser' at CCHH X'cchh'`

ECB = X'NN......' IOB = X'type' X'ecb' X'work1' X'work2'

X'chpgm' X'dcb' X'wkccw' X'mbb' X'cchh'

Nr-bytes-read = 'read'

Explanation: During a full-track read, an error condition was encountered. The Volser and the CCHH of the track, where the read failed, is reported. The contents of the IOB (40 bytes) is displayed for diagnosing the problem.

Solution: If the reason cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0108W 'nr' events were lost from following history record.`

Explanation: During the capture function, an inconsistent structure of events was encountered. The events are deleted.

Solution: If the reason cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0109W * Fingerprint Data Set is empty *`

DSname = 'data set name'

DDname = 'DD name'

Explanation: Fingerprint Data Set is empty. Process should be evaluated.

Solution: If the reason cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0110E Alloc Failure previously allocated volume, 'volser'`

Explanation: An SVC 99, request to allocate a volume, failed since it was already allocated.

Solution: If the reason cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0111T Site Master, 'cluster name' -added- key, 'record key'`

Explanation: This is a trace (or logging) message. The record of the specified key was added successfully to the Site Master VSAM cluster.

`HPS0112T KEY 'Site Master Key' UPDATED IN THE SITE MASTER FILE, 'ACB cluster name'`

Explanation: This is a trace (or logging) message. The record of the specified key was updated successfully in the Site Master VSAM cluster.

`HPS0113T KEY 'Site Master Key' ERASED FROM THE SITE MASTER 'ACB cluster name'`

Explanation: This is a trace (or logging) message. The record of the specified key was erased successfully from the Site Master VSAM cluster.

`HPS0114T KEY 'Object Master Key', ADDED TO THE OBJECT MASTER 'ACBCLUS'`

Explanation: This is a trace (or logging) message. The record of the specified key was added successfully to the Object Master VSAM cluster.

`HPS0115T KEY 'Object Master key' UPDATED IN THE OBJECT MASTER 'ACB cluster name'`

Explanation: This is a trace (or logging) message. The record of the specified key was updated successfully in the Object Master VSAM cluster.

`HPS0116T KEY 'Object Master key' ERASED FROM OBJECT MASTER 'ACB cluster name'`

Explanation: This is a trace (or logging) message. The record of the specified key was erased successfully from the Object Master VSAM cluster.

`HPS0117W Object Master "name" does not exist.`

Solution: If the reason cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0118W * REFERRED OBJECT MASTER ALREADY EXISTS * OBJECT MASTER CLUSTER NAME 'cluster'`

Explanation: The attempt to attach this Object Master to the Site Master is denied because it already is attached.

Solution: Make sure the Object Master cluster name is correct as given.

`HPS0119W * Error * OWNER NAME FIELD IS NULL`

Explanation: During the attach of an Object Master, the owner name was not provided.

Solution: Provide the name of the owner for the Object Master.

`HPS0120W * Error * null password field not flagged with "*"`

Solution: Provide the name of the owner for the Object Master.

`HPS0121W * Primary function cannot be selected. Userid is not a primary.`

Explanation: Userid must be a Site Master Administrator.

Solution: Contact the Site Administrator to perform the function.

`HPS0122W * Admin function cannot be selected. Userid is not an administrator on this OM.`

Explanation: Userid must be an OM Administrator on the current OM.

Solution: Contact the Site Administrator to perform the function.

`HPS0123W * Group Admin function cannot be selected. Userid is not an Admin in this OM.`

Explanation: Userid must be a Group administrator to perform the function.

Solution: Contact the Group Administrator to perform the function.

`HPS0124W * User function cannot be selected. Userid is not a user in current group.`

Explanation: Userid must be a user assigned by the Group Administrator.

Solution: Ask the Group Administrator to add the user.

`HPS0125W * Administrator/user functions cannot be selected. OM IS not attached.`

Explanation: An Object Master must be attached before an Object Master Administrator, Group Administrator or a User can perform functions against it.

Solution: Have the authorized person attach the Object Master, and try the function then.

`HPS0126W * Setgrp failed. Not in Group Admin or User mode.`

Explanation: This is probably an internal error.

Solution: If the reason cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0127W Dsn is cataloged on a non-DASD device. Dsn: 'dsn'`

Solution: None. Non-DASD data sets are not supported.

`HPS0128E Fingerprint Dsn 'dsn' failed the locate.`

Solution: Correct the probable error in the name.

`HPS0129E Fingerprint Dsn 'dsn' is not dsorg=PS,recfm=FB lrecl=512,blksize=4096`

Explanation: This is not a Fingerprint Data Set.

Solution: Correct the probable error in the name or the attributes.

`HPS0130W Volser list is required for uncataloged dsn, 'dsn'`

Solution: Provide the volser(s).

`HPS0131W Volume list conflicts with catalog on dsn, 'dsn' Catalog-list User-list`

Explanation: There is a conflict between what the catalog indicates and what the user assumes.

Solution: Resolve the conflict by checking the system catalog.

`HPS0132W Obtain failure on volume 'volser' Not added for tracking Dsn, 'dsn'`

Explanation: The data set to be tracked failed the Obtain.

Solution: Check the catalog or the VTOC of the volume to find out the location of the data set, and correct the data set name or the supplied volser.

`HPS0133W Invalid multi-volume sequence list for Dsn, 'dsn'`

Explanation: The multi-volume data set does not have proper sequencing.

Solution: Check the system catalog and correct the volume list.

`HPS0134E Open failure on Fingerprint Data Set`

Sname = 'Fingerprint Data Set name'

DDname = 'DD name pointing to the Fingerprint Data Set'

Explanation: Fingerprint Data Set did not open successfully.

Solution: Verify the dsname or the DD pointing to the Fingerprint Data Set.

`HPS0135E Close failure on Fingerprint Data Set 'Data set name'`

Explanation: The named Fingerprint Data Set could not be closed.

Solution: If the reason cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0136I Fingerprint Data Set created successfully containing tokens for 'nr' data sets. DSname = 'dsn' DDname = 'dd'`

`HPS0137E Locate failed with RC='code'`

Explanation: The locate macro failed.

Solution: Check the spelling of the name.

`HPS0138I Dsn selected and included, DSN`

Explanation: The data set specified was selected, by specification criteria, and was hashed successfully.

`HPS0139I * Dsn not selected, 'data set name'`

Explanation: The data set named in the message was a candidate for selection. It was not selected because it was a VSAM data set.

`HPS0140I Dsn not included , 'Data set name'`

Explanation: The data set named could not be hashed successfully. This message is preceded by an HPS07nn message indicating the reason for the failure.

`HPS0141I Volume selected, 'volser' Addr, 'cuu' Mounted-`

'storage/private/public'

Explanation: The volume was selected using a VOLSER pattern.

`HPS0142I Fingerprint Data Set loaded successfully.`

'nr' data sets included.'

'nr' data sets excluded.'

Dsname = 'dsn'

DDname = 'dd'

`HPS0143E Superdir already contains Todsn, 'data set name'`

Explanation: The Superdir data set already contains the information for this data set.

Solution: This job may have been submitted before.

`HPS0144W Inconsistent attributes in Multi-vol Dsn, 'dsn'`

Solution: Investigate the error. If the reason cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0145I SM-Key= 'key'`

(message indicating the Site Master key.)

`HPS0146E Target Dsn='Data set name'`

Lrecl='Lrecl' Blksize='Block size' Dsorg='Dsorg'

Recfm='RecFM'

Base Dsn='Data set name'

Lrecl='Lrecl' Blksize='Block size' Dsorg='Dsorg'

Recfm='RecFM Target has unmatching attributes with base

Explanation: A request to synchronize two groups of data sets was made. The data set attributes of the target and base must match. For example, if the target data set is a load library, the base data sets must all be load libraries as well.

Solution: Correct the unmatched situations, and resubmit the job.

`HPS0147I Targ-Dsn: 'dsn'`

`HPS0148W Open failure on dsn 'dsn'`

Solution: Correct the error.

`HPS0149E Aborted. Resolve the conflicts using the REJECT parameter and resubmit the job.`

Explanation: During the EXTRACT process, some conflicts have been detected. These conflicts should be resolved.

Solution: To run this function successfully, the identified conflicts must be resolved. Use the REJECT parameter.

`HPS0150I Successful open of DSN 'Data set name'`

Explanation: The defined Object passed all security checks successfully. It was opened for READ access.

`HPS0151E Fingerprint Data Set is Damaged or empty or had nothing selected.`

DSname = 'dsn'

DDname = 'dd'

Solution: Correct the error and resubmit.

`HPS0152I Pattern exclusion of dsn, 'dsname'`

Explanation: This data set is excluded due to the presence of the EXCLDSN parameter.

`HPS0153I Not included by pattern. Dsn, 'dsname'`

Explanation: The INCLDSN pattern was defined such that this data set was not selected.

`HPS0154W Duplicate name rejection of dsn, 'dsname'`

Explanation: The INCLDSN pattern was defined such that this data set was not selected.

`HPS0155W Targ-Dsn , 'DSN'`

`HPS0156E Target has multiple base but is not a PDS`

Explanation: The target, when multiple, must be PDS.

Solution: Correct the error and resubmit the job.

`HPS0157W Base-Dsn, 'DSN'`

`HPS0158W Like member names with unlike contents are conflicts.`

Explanation: In the base group there were multiple members having the same name, but being different in contents.

Solution: Decide which member is the correct one and delete the undesirable modules.

`HPS0159W Target Dsn already exists in Superdir 'DSN'.`

Explanation: Probably the job has been submitted twice.

`HPS0160W BASKET is empty, No action taken.`

Explanation: The BASKET used in the EXPORT function was empty.

Solution: Create another BASKET and resubmit the job.

`HPS0161W Empty data set, 'data set name'`

`HPS0162W Not a Superdir data set:`

Solution: Correct the DD to point to the appropriate Superdir data set.

`HPS0163W Damage type 'code'`

Explanation: The Superdir data set was found to be invalid.

Solution: This code must be interpreted by ChangeMan SSM Technical Support.

`HPS0164E Open failure for Superdir data set DSname='dsn' DDname='dd'`

Solution: Contact ChangeMan SSM Technical Support.

`HPS0165E Close failure on Superdir data set 'data set name'`

Explanation: This may be an internal problem.

Solution: Contact ChangeMan SSM Technical Support.

`HPS0166I Superdir data set created successfully.`

`HPS0167W Duplicate Dsname is flushed.`

`HPS0168I Successful recall of Superdir data set.`

`HPS0169W Non-PDS data set Fingerprint is changed for Dsn = 'source data set'`

Explanation: This is a non-partitioned data set. The Fingerprint token is different from what it is expected to be. Integrity question.

Solution: Correct the condition and resubmit the job.

`HPS0170W Member 'member name' has been updated.`

From-DSN, 'base data set name'

Explanation: During the EXPORT of a changed member, the Fingerprint token of the member to be exported was different from the one recorded in the super directory. There is a potential regression.

Solution: Determine the cause of the error and redo the EXTRACT, and REJECT these conflicting members. If REJECT is not wanted, re-Fingerprint the base environment.

`HPS0171W Member 'member name' was deleted from base DSN 'base data set name'`

Explanation: During the EXPORT of a changed member, the member to be exported no longer exists in the base environment.

Solution: Determine the cause of the error and redo the EXTRACT, and reject these conflicting members. If REJECT is not wanted, re-Fingerprint the base environment to establish a new representation.

`HPS0172W Close failure on dsn, 'dsn'`

Explanation: The data set did not close. This may be an internal problem.

Solution: Contact ChangeMan SSM Technical Support.

`HPS0173W HPSTRACK hh:mm:ss OPEN failed for 'cluster name'`

R15=n ACB error field=x'nn'

Uninitialized VSAM files are not supported.

Explanation: The data set did not open. An empty VSAM file is a common cause for the open failure when R15=8 and ACBERRF=x'A0'.

Solution: Contact ChangeMan SSM Technical Support if you cannot solve the problem.

`HPS0174W Defective history will have bytes removed between displacement 'address' and 'address'`

Explanation: There were bad events in the structure. This may be an internal problem.

Solution: Contact ChangeMan SSM Technical Support.

`HPS0175E Obtain DSCB1 error`

Explanation: The data set does not exist any more. There may be an invalid entry in the catalog that does not point to a valid data set.

Solution: Investigate the reason and correct the problem.

`HPS0176I Basket created successfully.`

Solution: Proceed with the IMPORT function if wanted at this time.

`HPS0177E Open failure for Basket.`

Solution: Check for the DD to make sure it is pointing to the correct data set.

`HPS0178E Close failure for Basket.`

Explanation: This may be an internal problem.

Solution: Contact ChangeMan SSM Technical Support.

`HPS0179E Not in VSAM mode for 'dsn'`

Explanation: This may be an internal problem.

Solution: Contact ChangeMan SSM Technical Support.

`HPS0180E Open failure of DDSOURCE`

Explanation: This DD is used internally by the ChangeMan SSM to perform EXPORT or IMPORT. This may be an internal problem.

Solution: Contact ChangeMan SSM Technical Support.

`HPS0181W End of basket.`

Solution: Investigate the problem. Make sure the DD is pointing to the correct data set.

`HPS0182W Not a Basket data set, 'data set name'`

Explanation: The data structure of this file is not consistent with a basket data set format.

Solution: Investigate the problem. Make sure the DD is pointing to the correct data set.

`HPS0183W Basket damage type 'nn' "Damage type description"`

Record nr: 'record_num'

Dsn:'dsn'

'basket_timestamp'

'basket_comment'

Basket ='basket_dsn'

DDname='basket_dd'

Explanation: During transfer of the basket, some unknown problem occurred. For the damage type code, refer to the MESSAGES member in the SAMPLES library. For information on how to prevent this from occurring, refer to the job SEND4KBS in the SAMPLES library. For some damage type codes, the "basket timestamp" and "basket comment" may display instead of the DSN.

Solution: If you cannot eliminate this problem, contact ChangeMan SSM Technical Support.

`HPS0184E Open failure for Basket data set 'data set name'`

Explanation: The basket data set failed to open. This may be an internal problem.

Solution: Contact ChangeMan SSM Technical Support.

`HPS0185E Close failure on Basket data set 'data set name'`

Explanation: The basket data set failed to close. This may be an internal problem.

Solution: Contact ChangeMan SSM Technical Support.

`HPS0186E Close failure on DD HPSWORK`

Explanation: This internally-used DD failed to close. This may be an internal problem.

Solution: Contact ChangeMan SSM Technical Support.

`HPS0187I Dsname is rejected`

Explanation: The data set did not match the Import pattern.

`HPS0188I Import completed successfully for Basket 'data set name'`

`HPS0189E Close failure on data set 'data set name'`

Explanation: This may be an internal problem.

Solution: Contact ChangeMan SSM Technical Support.

`HPS0190E Open failure of DD HPSWORK`

Explanation: This is a required DD for the operation of the batch facilities.

Solution: Make sure the HPSWORK DD has been provided.

`HPS0191I OM-Key= 'object master key'`

Explanation: The Object Master key involved is reported.

`HPS0192I Pgmflags= 'program flags'`

Explanation: Program flags are set for debugging purposes.

`HPS0193I 'FromDsn node' deleted from 'TargDsn node'`

Explanation: The data set node in the FROM chain is deleted.

`HPS0194E Open failure for redundancy data set name'`

Explanation: A DASDRED command refers to a DD that could not be opened.

Solution: Correct the DD to point to an appropriate physical sequential data set that will contain data set tokens.

`HPS0195E Close failure on DD 'name'`

Explanation: At the end of a DASDRED command the data set did not close successfully. This may be an internal problem.

Solution: Contact ChangeMan SSM Technical Support.

`HPS0196E File on DD 'name' is damaged.`

Explanation: The redundancy data set referred to in the DASDRED command does not have a valid data structure. The DD points to the wrong redundancy file or the file has been damaged.

Solution: If the reason cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0197I File successfully created on DD 'name'`

Explanation: The redundancy data set referred to by the DASDRED command has successfully been created.

Solution: Proceed with the other steps required to identify the redundant data sets or data set members.

`HPS0198W Jarea is damaged and object will not be updated.`

Explanation: There was an error in the structure of an event in the Site Master.

Solution: Contact ChangeMan SSM Technical Support.

`HPS0199E Vsam data sets are rejected.`

Explanation: VSAM files are not fingerprinted.

HPS0200-HPS0299

`HPS0200E Object record damaged: 'object name'`

Object will not be updated.

Explanation: The Site Master type 9 records (in the P-Area), for this object, may be damaged.

Solution: Delete and redefine the object to Change Tracking.

`HPS0201W Delta-tracking of PS or VS files is not supported.`

Explanation: The dataset has been defined to Change Tracking, however Delta Tracking has been set to NO.

`HPS0250I PDS has no tracked members: 'dsname'`

Explanation: The ZRF report issues this message. The specified library does not have any member names that match an existing MRT tracking entry, rc = 0.

Solution: Since this is informational only, the action depends on the user's intention in running the job. Take the appropriate action.

`HPS0251W PDS is not accessible: 'dsname'`

'reason'

'condition'

Explanation: The ZRF report issues this message. The specified library could not be accessed, rc = 4.

There are three possible reasons why the library could not be accessed:

Unable to allocate this library.
User does not have READ access.
OPEN error or abend occurred.

The possible condition is:

Activity not reported; at least one member reference found.

If condition displays, it indicates that one or more members in the library have been referenced, but ChangeMan SSM could not access the PDS to list the members that have not been referenced.

Solution: If ChangeMan SSM is unable to allocate the library, it is likely that another job has exclusive use of the dataset; verify that the user can have access to the dataset. If the user does not have READ access, verify that the user has the necessary security permissions to access the dataset. If there is an OPEN error or an abend, it is probable that the dataset has been corrupted; verify that the dataset is valid.

`HPS0252I OBTAIN failed for: 'dsname'`

Dataset missing (no format-1 DSCB found)

Explanation: The ZRF report issues this message. The dataset cannot be found, rc = 0.

Solution: Since this is informational only, the action depends on the user's intention in running the job. Take the appropriate action.

`HPS0253E MRT table not found.`

Explanation: The ZRF report issues this message. No MRT tracking entries were found in the Site Master file, rc = 8.

Solution: MRT requires at least one entry in the MRT table; ensure that tracking is enabled and there is something to track.

`HPS0254E (internal) Catlg work area empty`

Explanation: The ZRF report issues this message. This is an internal error, rc = 8.

Solution: Contact ChangeMan SSM Technical Support.

`HPS0255W Current PDS - 'dsname' contains more than 524287 members`

Remaining member names not included.

Explanation: The ZRF report issues this message. The specified library has more members than can be reported, rc = 4.

Solution: To report on all the members, the dataset must be split into smaller datasets.

`HPS0256E Wrong version (nnn) of the Site Master file.`

Explanation: The ZRF report issues this message. The job cannot use the specified version (nnn) of the SITEMSTR file, rc =12.

Solution: Ensure that the release level of the Site Master file matches that of ChangeMan SSM.

`HPS0257E SITEMSTR file empty or not valid.`

Explanation: The ZRF report issues this message. The job cannot use the SITEMSTR file, it is not a valid ChangeMan SSM Site Master, rc = 12.

Solution: Verify that a valid SITEMSTER file is available to ChangeMan SSM.

HPS0258E Unable to open MRTAUX3 file.

Explanation: Either the ZRF report or the MRT report issues this message. The MRTAUX3 file cannot be accessed by the job; the VSAM file containing captured member references is missing, damaged, or held by another job, rc = 12.

Solution: Verify that a valid MRTAUX3 file, not held by any other job, is available to ChangeMan SSM.

`HPS0259E Unable to open SITEMSTR file.`

Explanation: The ZRF report issues this message. The SITEMSTR file cannot be opened by the job; it is missing, damaged, or held by another job, rc = 12.

Solution: Verify that a valid SITEMSTR file, not held by any other job, is available to ChangeMan SSM.

`HPS0260I PDS has no referenced members: 'dsname'`

Explanation: The ZRF report issues this message. All members within the specified library remain unreferenced, rc = 0.

Solution: Since this is informational only, the action must depend on the user's intention in running the job. Take the appropriate action.

`HPS0261E Unrecognized Parameter: 'parameter input'`

or

Invalid FROM or TO date.

or

Invalid date range.

or

INCLUSIVE requires a date range.

Explanation: This message displays when there is a validation error with the MRTRP input parameters.

In the first case, a parameter has been found which is not recognized by the MRTRP job. See the Change Tracking User's Guide for the list of possible parameters.
In the second case, either the FROM or the TO date has been specified with an invalid value. See the Change Tracking User's Guide for the required date format.
In the third case, either the FROM date/time is later than the TO date/time, or the FROM or TO date is beyond the range of supported dates.
In the fourth case, INCLUSIVE was specified and either a FROM or a TO date was not specified.

HPS0300-HPS0399

`HPS0326E * Error * Object Master 1st record is invalid. Key of record is 'record key' and length='record length'`

Explanation: The first record (Record Type 0) of the Object Master was invalid. This may be an integrity problem.

Solution: Contact ChangeMan SSM Technical Support.

`HPS0327W * Error * Object Master record length is invalid. Key of record is 'record key' and length='record length'`

Explanation: The first record (Record Type 0) of the Object Master was found with an invalid length. This may be an integrity problem.

Solution: Contact ChangeMan SSM Technical Support.

`HPS0329I Successful open of Object Master: 'cluster'`

`HPS0330E * Failure to locate cluster 'cluster name'`

Explanation: The named Object Master could not be located in the system catalog.

Solution: The Object Master must be a VSAM data set.

`HPS0331E * Initialization aborted * R0 = 'content'`

Explanation: The initialization process is aborted due to a volume allocation error. Register 0 contains the program return code.

Solution: If the reason cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0332E OM data component not found in VVDS.`

Cluster name='cluster name'

Explanation: Since the VSAM data component of the Object Master was not found in the VVDS (VSAM Volume Data Set), it is not a legitimate VSAM data set.

Solution: If the reason cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0333I * Object Master remains in sequential mode.*`

Explanation: The Object Master was opened for random processing; it was discovered to be a new file and then opened for sequential processing.

`HPS0334I Max-lrecl = 'maximum relic'`

Max-data = 'maximum data size'

Explanation: After a VSAM file (the Object Master) is located in the VVDS (VSAM Volume Data Set), both the CI and Maximum Record Size are logged. This is associated with message HPS0333I when the file is VSAM.

HPS0500-HPS0599

`HPS0500E Delta Master was not specified in the HPSPARMS member.`

Explanation: The name of the Delta Master must be specified in the HPSPARMS member.

Solution: Edit the HPSPRAMS member to include this parameter. Refer to the ChangeMan SSM Installation Guide for details.

`HPS0501E IEBCOPY failed with 'S'`

Solution: Determine the cause of IEBCOPY failure. Correct the problem and resubmit the job.

`HPS0501W IEBCOPY failed with RC= 'return code'`

Explanation: A return code of 24 may indicate that the HPSWORK or HPSWORK2 DDs are missing from the JCL. Refer to the ChangeMan SSM Detection and Synchronization Guide for information on coding these DD statements.

Solution: Determine the cause of IEBCOPY failure. Correct the problem and resubmit the job.

`HPS0502I Delta Master cluster has been initialized.`

Max-lrecl = 'maximum lrecc'

Max-data size = 'maximum data size'

Explanation: The first time the Delta Master is opened for output, it is initialized.

`HPS0503E Delta Master first record is invalid.`

Explanation: The integrity of Delta Master is questionable.

Solution: Execute the HPSMAINT program ($MAINT JCL) with no parms to identify and correct the database. Contact ChangeMan SSM Technical Support.

`HPS0504I Successful open of Delta Master, 'database name'`

`HPS0505E * Failure of cluster name locate * for cluster 'cluster name'`

Solution: Determine the problem. Contact SSM Technical Support.

`HPS0506E Delta Master cluster not found in VVDS.`

Solution: Contact ChangeMan SSM Technical Support.

`HPS0507E Volume 'volser' is not online.`

Explanation: The pattern specified indicated a volume that is off-line.

Solution: Bring the volume on-line or use EXCLVOL command to exclude such volumes.

`HPS0508E Obtain failure on volume 'volser' Failure to update Dsn, 'dsn'`

Explanation: The data set did not exist. The data set name may have been specified incorrectly.

Solution: Correct the problem and repeat the function.

`HPS0509W ==> Basket should not be used. <==`

        `*********************************************`
        `* 1. If there were errors or warnings, they *`
        `*    should be corrected before rerunning.  *`
        `* 2. If the Base environment has changed    *`
        `*    since it was Fingerprinted, then       *`
        `*    re-Fingerprinting is required.         *`
        `*                                           *`
        `* If both environments are in sync,         *`
        `* there is nothing to do.                   *`
        `*********************************************`

Explanation: This is the safeguard feature of ChangeMan SSM. The EXTRACT/EXPORT function encountered one or more members for which the tokens are now different from what is noted in the Fingerprint Data Set.

Solution: Re-Fingerprint the BASE environment to reflect the new environment.

`HPS0510W Import was completed with some warnings. Review the warning messages, and perform a subsequent IMPORT/APPLY for the identified data sets as required.`

Explanation: Time-stamp. One or more warnings were encountered during IMPORT.

Solution: Check the SYSPRINT for those failed data sets. Resubmit the job and INCLUDE the data sets that need to be IMPORTED again.

`HPS0511T ** Delta Master: name updated key: value`

Explanation: This is a trace (or logging) message.

`HPS0512T ** Delta Master: name removed key: val`

Explanation: This is a trace (or logging) message.

`HPS0513W Failure Dynamic de-allocation of DD 'ddname'`

SVC 99 error field = 'error code' info = 'information code'

Explanation: Failure to deallocate the DD.

Solution: Follow the instructions described in message HPS0100W to determine the cause of the error. If the cause cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0514E ** Delta Master cluster initialization aborted. R0 =' '`

Explanation: First-time initialization of Delta Master failed.

Solution: If the reason cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0515W Tracking rejected for 'data set name' It is cataloged to pseudo volume 'volser'`

Explanation: The data set has been either migrated (HSM) or archived (SAMS:DISK or DMS). These data sets are identified in the report.

Solution: Recall the data set if required, or rerun the job with AUTORECALL=Y specified

`HPS0516W Cataloged dsn, 'data set name' is currently pointing to pseudo volume 'volser' Object is unavailable for tracking.`

Explanation: The data set has been either migrated (HSM) or archived (SAMS:DISK or DMS); therefore, it is not available for tracking.

Solution: Recall the data sets, if required, and restart the CAPTURE function.

`HPS0518W Dsn is not cataloged, 'data set name'`

Explanation: During the IMPORT function, the parameter TOVOL=* was specified. The specified data set, which is to be updated in the target environment, is expected to be cataloged.

Solution: Determine the cause of the error. Specify OLDDSNTOVOL=volser parameter to point to the volume where the data set is to be updated.

`HPS0519W Invalid DSCB1 attribute combination.`

Dsname = 'dsn'

Volser = 'volser'

DS1DSORG = 'ds1dsorg'

DS1RECFM = 'ds1recfm'

DS1LRECL = 'ds1lrecl'

DS1BLKL = 'ds1blkl'

Solution: Correct the error and resubmit.

`HPS0520W Incompatible mask. Rejected: 'mask'`

Solution: Correct the error and resubmit.

`HPS0521W Structure verification failure on track 'cchh' of volume 'volser' CKD failed. 'cchh' expected but 'cache' was found.`

Solution: Do an analysis on CCHH.

`HPS0522W Dsn: 'dsn'`

Explanation: Non-PDS data sets are rejected with masking in effect.

Solution: If the reason cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0523W Import was completed with exceptions for BASKET`

DSNAME=DSN

DDNAME=BASKETDD

Solution: Review report to find DSN issuing warning and take necessary action.

`HPS0524W Cataloged dsn 'dsn' is currently pointing to pseudo volume 'volser'`

Explanation: The data set is migrated or archived, and is skipped.

Solution: To process migrated and archived data sets, specify the AUTORECALL=Y command.

`HPS0525E Catalog Search Interface failure.`

MODID= 'module ID'

RETURNCODE= 'return code'

REASONCODE= 'reason code'

* Program return code = 0525 *

Explanation: There was a CSI error due to an invalid DSN pattern.

`HPS0525W Catalog Search Interface failure for this DSN.`

Dsn: 'dsn'

MODID= 'module ID'

RETURNCODE= 'return code'

REASONCODE= 'reason code'

Explanation: There was a CSI error for a single DSN entry.

`HPS0526W Catalog search work area too small for results from`

requested DSN pattern: 'pattern'

Last entry processed was Dsn: 'dsn'

Use multiple DSN patterns that return fewer results.

Explanation: A partial DSN list has been returned due to insufficient storage.

`HPS0527E Insufficient storage, retry with larger region size.`

Explanation: SSM could not obtain the storage requested for the catalog work area.

`HPS0528E Unable to load IGGCSI00 - Catalog Search Interface.`

Explanation: The IGGCSI00 (CSI API) module could not be loaded.

`HPS0529E Conflict of transformed names: 'transform'`

Pretransformed original 1st name : 'transform1'

Pretransformed original 2nd name : 'transform2'

Solution: Correct the error and resubmit.

`HPS0530E Open failure on DD HPSSCR`

DSN = 'dsn'

Solution: Correct the error and resubmit.

`HPS0531E HPSSCR was supplied but SCRATCH option was not.`

Solution: Remove HPSSCR if it is not needed, or specify SCRATCH.

`HPS0532E Option SCRATCH was specified, but DD HPSSCR was not.`

Solution: Supply the DD and resubmit the job.

`HPS0532W Failure Dynamic deallocation of DD RECALLDD SVC99 error field = "error code", info = "info code",`

Solution: Check the DD and resubmit the job.

`HPS0533E Close failure on dd HPSSCR.`

Solution: Contact ChangeMan SSM Technical Support.

`HPS0534I 'nr' scratch commands written to file: 'dsn'`

`HPS0535E Obtain DSCB1 error.`

DSname = 'dsn'

Volser = 'volser'

Solution: Contact ChangeMan SSM Technical Support.

`HPS0536I Reverse Basket created successfully.`

Explanation: The Reverse Change Basket has been created successfully.

`HPS0537E Open failure for Reverse Basket`

Dsname= 'Reverse basket DSN'

Ddname= 'DDNAME'

Explanation: The Reverse Change Basket failed to open.

Solution: Check the DD to determine the cause.

`HPS0538E Close failure on Reverse Basket`

Explanation: The Reverse Change Basket failed to close. This may be an internal error.

Solution: Contact ChangeMan SSM Technical Support.

`HPS0539E Open failure of 'Reverse basket DD'`

Explanation: The Reverse Change Basket failed to open.

Solution: Check the DD to determine the cause.

`HPS0540W ==> Reverse Basket should not be used. <==`

`* * * * * * * * * * * * * * * * * * *`
`* Warning or Errors have occurred.  * `
`* * * * * * * * * * * * * * * * * * *`

Explanation: The Reverse Change Basket should not be used. Its integrity is not assured.

Solution: If the reason cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0541W Allocation of volume "volser" failed. not ONLINE.`

Solution: Check the referenced volser for its availability.

`HPS0542W Volume "volser" is not online. Object cannot be defined for tracking: "dsname"`

Solution: Check the referenced volser for its availability.

`HPS0543I Tracking of ChangeMan SSM data bases is rejected.`

Explanation: The VSAM data set being defined to the Audit component is a ChangeMan SSM data base. It is, therefore, rejected.

`HPS0544W Failure Dynamic allocation of member: "member name" DS name:"dsname". SVC99 error field ="error code" info = "info code"`

Solution: Follow the instructions described in message HPS0100W to determine the cause of the error.

`HPS0545I Selective Fingerprinting for cluster:"cluster name"`

`HPS0546W Failure Dynamic deallocation of DD "ddname"`

SVC99 error field = "error code" info = "info code"

Solution: Follow the instructions described in message HPS0100W to determine the cause of the error.

`HPS0547W COMPAREX failed with "system RC"`

Solution: Check to see if COMPAREX load library is in the STEPLIB concatenation. If the cause cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0548W COMPAREX failed with RC="COMPAREX RC"`

Solution: Contact ChangeMan SSM Technical Support.

`HPS0549W SUPERC failed with "System RC"`

Explanation: IBM SuperC may not be in a linklisted library.

Solution: If the reason cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0550W SUPERC failed with RC= "SuperC RC"`

Solution: Contact ChangeMan SSM Technical Support.

`HPS0551I TYPE exclusion of dsn: "dsname"`

Explanation: The type of the excluded data set does not match the TYPE parameter requested.

Solution: No action required.

`HPS0552E FGP was created with a previous version of SSM.`

Process only with previous version of software.

DSN= 'DSN'

Solution: Apply the FGP with the earlier version of ChangeMan SSM, or recreate the FGP using the new version.

`HPS0553E FGP has been altered. Rejected DSN: 'DSN'`

Solution: Verify the integrity of the FGP data set.

`HPS0554W Change Basket could not be created, DSN already cataloged.`

Solution: If you are unable to resolve the problem, contact ChangeMan SSM Technical Support.

`HPS0555I Base Target`

'num' 'num' Member name matches

'num' 'num' Synchronized members

'num' 'num' Out of sync members

'num' 'num' Member name mismatches

`HPS0555W Base Target`

'num' 'num' Member name matches

'num' 'num' Synchronized members

'num' 'num' Out of sync members

'num' 'num' Member name mismatches

Explanation: Some members were out of sync, or had name mismatches.

Solution: Evaluate the reason for the discrepancy.

`HPS0556I Volume 'SOURCE' replaced with 'TARGET'`

`HPS0557W SCRATCH failed on DSN 'DSNNAME' Rename required for 'DSN'`

`HPS0558W RENAME of TEMP Dsn 'DSN' to original name 'OLDNAME' failed. Use standard rename before it is available.`

Solution: Rename the DSN manually so that it may be used.

`HPS0559I Attempting INFO API connect.`

`HPS0560I INFO Connection complete.`

`HPS0561I Disconnecting from INFO API.`

`HPS0562I Unable to load BLGYSRVR - INFO API INFO Connection disabled.`

`HPS0563I PIDT 'pidt' creation successful.`

`HPS0564W Not a real PIDT - AbaNone.`

`HPS0565W INFO; Structure word not found, SWORD='hhhhhhhh'`

`HPS0566W INFO; Tran= 'tran' RC= 'nn' REASON= 'nn'`

`HPS0567I Replaced Alias name: 'ALIASDSN' with "Real" DSName:'DSN'`

`HPS0568W IEBCOPY completed with RC='num'`

Solution: Determine the reason for the IEBCOPY failure and resubmit the job.

`HPS0569W Basket created with EXCEPTIONS. Use only with caution! At IMPORT time the questionable data sets could be excluded.`

'BASKET'

'COMMENT'

Explanation: Exceptions were encountered during the creation of the Basket.

Solution: Determine the problem. If assistance is required, contact ChangeMan SSM Technical Support.

`HPS0570I 'MEMBER' <REJECTED> 'TARGDSN'`

`HPS0571I Reverse Basket Entry: 'REV_TYPE = REV_DSN'`

`HPS0572E CHECKSUM failure loading DSN: 'DSN'`

Can continue only if EXCLDSN parameter is supplied.

Explanation: The CHECKSUM for the DSN did not match.

Solution: Use the EXCLDSN parameter to exclude the DSN, or determine the cause of the problem.

`HPS0573I Duplicate DSN rejected. Volser='VOLSER'`

DSN='DSN'

Already on tree Volser='VOLSER'

DSN='DSN'

`HPS0575I Fingerprints loaded for DSN: 'DSN'`

`HPS0577W Dsn 'data set name'`

has invalid attributes for an FGP data set.

Attribute Required Actual

Dsorg PS 'dsorg'

Recfm FB 'recfm'

Lrecl 512 'lrecl'

BlkSize 4096 'BlkSize'

`HPS0578W OPEN failed. READ access not authorized.`

Volume: 'volser', DSN: 'dsn'

Explanation: The user does not have authorization to read the data set, so it cannot be fingerprinted or defined to Change Tracking.

`HPS0579W Data set is already defined to an object by another type. Objects with a specific VOLSER take priority over objects defined by catalog.`

Object: 'data set name' 'volser'

Explanation: If the same physical data set is defined both by catalog and by VOLSER, then the object defined by VOLSER will take precedence and have the events attributed to it. Only the batch/online/global capture events will update the object defined by catalog.

`HPS0580W The DSORG for data set 'data set name' has changed and it will no longer be tracked. To continue tracking this data set, delete and redefine the object.`

Explanation: When the DSORG changes for a data set that is already being tracked (and is not pending), it will no longer be tracked.

Solution: To continue tracking this data set, delete and redefine the object.

HPS0600-HPS0699

`HPS0600W * Warning * Volume 'volser' has more than one VVDS`

Explanation: During the allocation of the named volume, more than one VVDS (VSAM Volume Data Set) was detected on the volume. This may be an integrity problem.

Solution: Determine the problem. If assistance is required, contact ChangeMan SSM Technical Support.

`HPS0601W * Warning * VVDS SYS1.VVDS.Vvolser CCHHR X'cccchhhhrr' disp X'nnnn' has a zero length entry. Rest of CI is skipped.`

Explanation: During the allocation of the named volume, a zero-length entry was found on the VVDS (VSAM Volume Data Set). This may be an indication of an integrity problem in the VVDS.

Solution: Determine the problem. If assistance is required, contact ChangeMan SSM Technical Support.

`HPS0602T * Warning * VVDS SYS1.VVDS.VVOLSER CCHH-R "value" DISP "value" has invalid entry type "type".`

Explanation: This is a trace (or logging) message.

Solution: Contact your DASD Administrator.

`HPS0603W * Warning * VVDS SYS1.VVDS.Vvolser CCHHR X'cccchhhhrr' disp X'nnnn' has invalid entry format.`

Explanation: During the allocation of the named volume, an unknown entry format was found on the VVDS (VSAM Volume Data Set). This may be an integrity problem.

Solution: Contact ChangeMan SSM Technical Support.

`HPS0604I Clus-name = "name"`

Comp-name = "name"

Time-stamp "value"

"rba" High-used-RBA

"rba" Component-RBA

"nr" Total-recs

"nr" Deleted-recs

"nr" Updated-recs

"nr" Relative-key-position

"nr" Key-length'

`HPS0605W VOLSER 'volser' is not online.`

Explanation: The named volume is not online.

Solution: If specified incorrectly, correct the volume specification, and resubmit the job. Or, vary the volume online and resubmit the job.

`HPS0607E * I/O read failure on volume 'volser' at CCHH X'cchh' ECB = X'NN......'`

IOB = X'type' X'ecb' X'work1' X'work2' X'chpgm'

X'dcb' X'wkccw' X'mbb' X'cchh'

NR-BYTES-READ = 'read'

Explanation: During a full-track read, an error condition was encountered. The Volser and the CCHH of the track where the read failed is reported. The contents of the IOB (40 bytes) are displayed for diagnosing the problem.

Solution: If the reason cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0608W Volser 'VOLSER' is not an MVS device.`

Explanation: The volume is not recognized as an MVS DASD.

Solution: If the reason cannot be determined, contact ChangeMan SSM Technical Support.

HPS0700-HPS0799

`HPS0700W * Warning * DSCB1 does not exist for 'data set name'`

Volser = 'VOLSER' FGP Tokens not generated.

Explanation: There may be an invalid entry in the catalog; however, the actual data set does not exist on the volume.

Solution: Determine the cause of the problem, or contact ChangeMan SSM Technical Support.

`HPS0701W * Warning * Cluster does not exist for 'data set name'`

Explanation: The named data set must be a VSAM data set. This data set has no entry in the VVDS (VSAM Volume Data Set). This is not a valid VSAM file.

Solution: Ensure that the named data set is a legitimate VSAM file. If not, correct the JCL, and resubmit the job.

`HPS0702W DSN = 'Data set name'`

* Error * relative TRK nr is too large 'cchh'

FGP Tokens not generated.

Explanation: An extent for the named data set is not a valid track number. The relative track address is too large and does not exist. The data set is probably opened for update by some other job.

Solution: Resubmit the job or execute the function when the data set is not in use.

`HPS0703E Duplicate key detected.`

DSN = 'data set name'

Explanation: A duplicate key was detected during Fingerprinting of a Keyed Flat File.

Solution: Verify that the KEY field is properly specified and is unique.

`HPS0703W Begin TTR not found 'cchhr' Member 'Nr' OF 'Total count'`

member name 'member' of DSN 'data set name'

Explanation: The beginning address of the extent (TTR) for the named member of this PDS is invalid. The data set is probably opened for update by some other job.

Solution: Resubmit the job or execute the function when the data set is not in use.

`HPS0704W CCHHR 'cchhr' of DSN 'data set name' has an invalid segment length. FGP Tokens not generated`

Explanation: In a variable blocked (VB) data set, the length of the block does not conform with the RDW of the record. The data set cannot be processed.

Solution: Investigate and correct the cause of the inconsistency, and resubmit the job.

`HPS0705W Member-name = 'member' DSN = 'data set name' * Error * Relative TRK nr is too large 'ttr'`

Explanation: An extent for the named data set member is not a valid track number. The relative track address is too large and does not exist. Data set integrity is questionable.

Solution: Investigate and correct the cause of the integrity problem and resubmit the job.

`HPS0706W CCHHR 'cchhr' OF DSN , 'Data set name' has an LRECL X'nnnn' and a block of length X'nnnn' FGP tokens not generated.`

Explanation: In a fixed blocked (FB) data set, the block size was not found to be a multiple of the record size. The track address of the inconsistency is reported. Data set integrity is questionable.

Solution: Investigate and correct the cause of the integrity problem and resubmit the job.

`HPS0707W CCHHR 'cchhr' of DSN , 'Data set name' has a blk-descriptor X'nnnn' and a blk-length of X'nnnn'`

Explanation: In a variable blocked (VB) data set, the block descriptor word does not conform with the actual number of bytes in the record. Data set integrity is questionable. FGP Tokens are not generated.

Solution: Investigate and correct the cause of the integrity problem and resubmit the job.

`HPS0708W CCHHR 'cchhr' OF DSN , 'Data set name' HAS A SEGMENT`

DESCRIPTOR OF X'nnnn'

FGP tokens not generated.

Explanation: In a variable blocked (VB) data set, the segment descriptor word does not conform with the actual number of bytes in the record. Data set integrity is questionable.

Solution: Investigate and correct the cause of the integrity problem and resubmit the job.

`HPS0709W Volume 'volser' allocation failed. RC='rc'`

Solution: Correct the error and resubmit.

`HPS0710W DSN is not PS, DA or PO Dsn='data set name'`

FGP tokens not generated.

Explanation: Fingerprinting of a non-Vsam data set was encountered. To fingerprint a data set, it must be any of the above DSORGs.

Solution: Investigate the source of the problem and resubmit the job.

`HPS0711I No volume list supplied`

Explanation: Processing a multi-volume data set, the list was not supplied to the program. This is probably an internal error.

Solution: Contact ChangeMan SSM Technical Support.

`HPS0711W No volume list supplied`

Explanation: While processing a multi-volume data set, the list was not supplied to the program. This is probably an internal error.

Solution: Contact ChangeMan SSM Technical Support.

`HPS0712E short key found:`

Dsn= 'data set name'

Explanation: The record was not long enough to allow a complete key.

Solution: Verify that the correct KEY field has been specified.

`HPS0713W PDS directory is damaged for dsn 'data set name'.`

Explanation: The directory of the PDS does not have a valid structure.

Solution: Exclude this data set by providing the EXCLDSN parameter of the BASE or TARGET command. If this does not solve the problem, contact ChangeMan SSM Technical Support.

`HPS0714W Obtain error for continuation DSCB in 'data set name'.`

FGP Tokens not generated.

Explanation: The OBTAIN macro encountered an error.

Solution: Exclude this data set by providing the EXCLDSN parameter. If this does not solve the problem, contact ChangeMan SSM Technical Support.

`HPS0715W ChangeMan SSM will consider member "name" to be an alias of member "name", since they share the same TTR "ttr"`

Solution: Investigate to verify that this member is an alias.

`HPS0716W Vsam component is disallowed. Comp, 'component name' Specify the cluster name.`

Solution: Cluster name must be specified. Correct and resubmit.

`HPS0717E Failure to define for Delta tracking. Object="dsname"`

Solution: If the reason cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0718T Delta Master:"cluster name" key zero updated.`

Explanation: This is a trace (or logging) message.

`HPS0719T Delta Master:"cluster name" added comp/expan-key:"value"`

Explanation: This is a trace (or logging) message.

`HPS0720I File is too small for compression. Size= 'size' No comp/expand table generated' for dsn, 'dsn'`

Explanation: The PDS being defined for delta tracking was less than 32k in size; therefore, the members are not compressed. When the data set grows beyond 32k, it will be compressed. The members, however, are still backed up in the Delta Master.

`HPS0720T File is too small for compression. Size= 'size' No comp/expand table generated' for dsn, 'dsn'`

Explanation: This is a trace message. The PDS being defined for delta tracking was less than 32k in size; therefore, the members are not compressed. When the data set grows beyond 32k, it will be compressed. The members, however, are still backed up in the Delta Master.

Solution: None. If these messages need to be suppressed, specify TRACE OFF.

`HPS0721I HPSDSFTP hh:mm:ss Compression is less than 'value'%. No comp/exp table generated for dsn: 'dsn'`

Explanation: During a DEFINEDS operation, the PDS being defined for delta tracking was less than 32k in size; therefore, the members are not compressed. When it grows beyond 32k it will be compressed at that time. The members, however, are backed up in the Delta Master.

`HPS0722W No extents in DSN 'data set name' This is an invalid data set.`

Solution: Determine the cause of the problem. If the cause cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0723I VTOC index files will not be fingerprinted: 'dsn'`

`HPS0724I VVDS files will not be tracked: 'dsn'`

`HPS0725I Unloadable load module: 'Module name'`

in library: 'Library name'

Re-link of the module may be required.

Explanation: The load module size from the attribute fields is smaller than the true size of the load module.

Solution: Re-link the module to correct the size specified in the user field.

`HPS0727W Lrecl=0 Blksize=0 DSN = 'data set name'`

FGP Tokens not generated

Explanation: The data set has invalid attributes, and was not Fingerprinted.

Solution: Verify the validity of the data set.

`HPS0728E Directory entry 'directory entry' is out of sequence.`

Dsn: 'data set name',

Data set processing is incomplete.

Explanation: The directory of the data set contains two entries with the same name, or the entries are not in ascending sequence by name.

HPS0800-HPS0899

`HPS0800I Output file successfully created.`

Explanation: The intermediate file for Redundancy Management is created successfully.

`HPS0801E Input file is damaged.`

`HPS0802E Open failure on input file`

Solution: Correct the error and resubmit the job.

`HPS0803E Close failure on input file`

Solution: Correct the error and resubmit the job.

`HPS0804E Unrecognized parm in execute parm`

Solution: Correct the error and resubmit the job.

`HPS0805E Duplicate parm in execute parm`

Solution: Correct the error and resubmit the job.

`HPS0806E Execute parm exists but has no parameters`

Solution: Correct the error and resubmit the job.

`HPS0807I ' R E D U N D A N C Y S U M M A R Y (DSN) `

nr Redundant groups

nr Included dsns

nr Highest redundancy level

nr Total allocated tracks in all groups

nr Total used tracks in all groups

nr Recoverable tracks from all groups

Explanation: The parameter DSN indicated that a "data set level" report was requested.

`HPS0808I ' R E D U N D A N C Y S U M M A R Y (MEM) `

nr Redundant groups

nr Included members

nr Highest redundancy level

nr Total bytes in all groups

nr Total used tracks in all groups

nr Recoverable tracks from all groups

Explanation: The parameter MEM indicated that a "member-level" report was requested.

HPS0900-HPS0999

`HPS0900I EOF HPSIN, Cards read='count' with 'nn' commands.`

Explanation: The message indicates the end-of-file status of the SYSIN data set for the batch synchronization function.

`HPS0902I Volume "volser" selected.'`

Explanation: The named volume was selected for processing.

`HPS0903I Pattern include of DSN in 'base/Target' dsn.`

Explanation: Information, the pattern entered is part of base or target data set.

`HPS0903T Dsorg= "value" Recfm="value" Selected-DSN="dsname".`

Explanation: This is a trace (or logging) message.

`HPS0904I "dsname" DSN added to "base/target" environment.`

Explanation: The specified data set is successfully Fingerprinted and the tokens are added into memory above the line.

`HPS0905I 'base/Target' Fingerprint Data Set saved successfully.`

Explanation: The specified data set is successfully Fingerprinted and the tokens are added into memory above the line.

`HPS0906I Fingerprint Data Set loaded to the 'base/target'`

Explanation: The named Fingerprint Data Set, requested by the LOAD parameter, was recalled and utilized in establishing the base or target Group.

`HPS0907I DSN not included by pattern on 'base/target' 'data set name'`

Explanation: In establishing the base or target environments, the INCLDSN parameter was provided. The data sets not included are reported for verification only.

`HPS0908I Pattern exclude of DSN on 'base/target' 'data set name'`

Explanation: In establishing the base or target environments, the EXCLDSN parameter was provided. The data sets thus excluded are reported for verification only.

`HPS0909W New DSN is already in Superdir, 'data set name'`

Explanation: During the execution of the EXTRACT command, the NEWDSN parameter was specified. The new data set was found; it already exists in the super directory.

`HPS0910E Memtomem target DSN not found.`

Explanation: The data set specified for processing from the target Group was not found. A compare mode of MEMTOMEM refers to two data sets, one in the base Group and the other in the target Group.

Solution: Ensure that the data set name is specified correctly. If the target Group was built by loading a Fingerprint Data Set and the contents are unknown, run the job with LIST=TARGET to determine the data sets on the Fingerprint Data Set.

`HPS0911I "nr' of "nr" Data sets Fingerprinted.`

`HPS0912I Base/Target`

nn Nr of DSNs in group.

nn Nr of non-PDS DSNs in group.

nn Total non-PDS hashed bytes.

nn Nr of PDS DSNs in group

nn Total PDS hashed bytes.

nn Nr of PDS members in group.

nn Nr of identical sets.

nn Total bytes of 1st elements in identical sets.

nn Nr of redundant entries in identical sets.

nn Total redundant bytes in identical sets.

nn In sync occurrences.

nn Out of sync occurrences.

nn Non Orphaned aliases.

nn Orphaned aliases.

Explanation: Base/Target=LIST was requested. The above statistics are reported. For an explanation of the redundancy statistics, refer to the message HPS0913I.

`HPS0913I Base(+) Target(-)`

nr nr Nr of DSNs in group.

nr nr Nr of non-PDS DSNs in group.

nr nr Total non-PDS hashed bytes.

nr nr Nr of PDS DSNs in group

nr nr Total PDS hashed bytes.

nr nr Nr of PDS members in group.

nr nr Nr of identical sets.

nr nr Total bytes of 1st elements in identical sets.

nr nr Nr of redundant entries in identical sets.

nr nr Total redundant bytes in identical sets.

nr nr In sync occurrences.

nr nr Out of sync occurrences.

nr nr Non Orphaned aliases.

nr nr Orphaned aliases.

Explanation: During synchronization of the base and target Groups, the above statistics were accumulated. If redundancy management was the purpose of this job, then refer to the redundancy information. Data sets or data set members with identical tokens create a set of identicals. The number of such sets, as well as the total number of redundant members (content duplicate regardless of name), are reported. It is assumed that within each set only one needs to be kept and the rest can be discarded. The total bytes of such first members are reported along with the total for all other members in the set. Also, the number of data sets or data set members that are in sync and outsync are reported.

Solution: Since this is informational only, the action must depend on the user's intention in running the job. Take the appropriate action.

`HPS0914W No Volume found matching Volume Selection criteria.`

Explanation: There are no volumes matching your selection.

Solution: Verify the correct volume and reenter.

`HPS0915I Superdir data set saved successfully on DD 'ddname'.`

Explanation: The super directory, the road map for synchronization, was successfully created in memory and saved on the external file pointed to by the DD.

`HPS0916I Added to Superdir: NewDSN = "dsname"`

`HPS0916W Not added to Superdir: NewDSN = "dsname"`

Explanation: Duplicate-name data sets were encountered in the base/target commands. A data set is only added once.

`HPS0917I Unmovable DSN rejected from Superdir, 'data set name'`

Explanation: During the execution of the EXTRACT command, the NEWDSN parameter was specified. A new data set was found; however, its attributes indicated that it was an unmovable data set. Such data sets will not be placed in the super directory.

`HPS0918I Added to Superdir, Olddsn = 'dsn'`

Explanation: The data set being extracted is added to the super directory for later export.

`HPS0919W * C L O C K T I M E E X P I R E D *'`

Explanation: During the Fingerprinting of a group of data sets, a volume or a pool of volumes, the CLOCK command was specified. Once the specified clock time is expired, the job terminates normally. The process can later be resumed by the RESTART command.

Solution: Resume the process at a later time using the RESTART command.

`HPS0920I Partitioned Data Sets compared, nr`

Base

Target S u m m a r y

nn nn Member name matches

nn nn Synchronized Members

nn nn Out of Sync members

nn nn Member name mismatches

nn nn Aliases (Non Orphaned)

nn nn Orphaned aliases

Explanation: During the compare mode DSNbyDSN, the above statistics are produced.

Solution: Since this is informational only, the action must depend on the user's intention in running the job. Take the appropriate action.

`HPS0921W Volume 'volser' is not online.`

Solution: Bring the volume online, and resubmit the job.

`HPS0922E Pgm is terminated. Required volume is not available.`

Solution: Bring the volume online if desired.

`HPS0923W Datasets: 'base dsn' and 'target dsn' * cannot be compared. * One data set is in compressed format; the other is not.`

Explanation: The base data set and target data set cannot be compared due to incompatible format. Both data sets must be in the same format.

Solution: Correct the format and resubmit.

`HPS0924I nn Data sets in Base`

nn Data sets in Target

nn Data set name matches

nn In-Sync data sets

nn Out-of-Sync data sets

nn data set name mismatches

Explanation: A compare mode of DSNtoDSN refers to two data sets, one in the base Group and the other in the target Group. The primary element for this comparison is data set name. Once a name match is determined, the token values (contents) are examined to specify a sync or outsync condition.

Solution: Since this is informational only, the action must depend on the user's intention in running the job. Take the appropriate action.

`HPS0925I Excluded DSN: 'dsn'.`

Explanation: Information, the specified data set has been excluded.

`HPS0926I Volser = 'volser' Dsn=' '`

`HPS0927I Dsn has 'nr' aliases and 'nr' orphans`

`HPS0928I Alias / Orphan report Summary:`

nr dsn in Base/Target

nr dsns have aliases

nr total orphaned aliases

nr total non-orphaned aliases

`HPS0929I Dsn has 'nr' non-standard member name`

`HPS0930I Non-standard member name Summary`

nr dsns in Base/Target

nr dsns have non-standard member names

nr TOTAL Non-standard member names

`HPS0931W No data sets added to 'base or target'`

from generic pattern 'pattern'

Explanation: The pattern did not resolve to any available data set.

Solution: Correct the pattern and resubmit the job.

`HPS0932I Short DsnByDsn Summary report:`

UnMatched data sets

'number' UnMatched Base data sets with

'number' members

'number' UnMatched Target data sets with

'number' members Matched data sets:

'number' Total matched data sets

'number' Total in sync data sets

'number' Total out of sync data sets

'number' Total in sync members

'number' Total out sync members

'number' Total base member mismatches

'number' Total target member mismatches

`HPS0933W Rejected HSM-migrated DSN, 'data set name'`

Explanation: An HSM-migrated data set was encountered.

Solution: Recall the data set, if desired, and re-submit the job.

`HPS0934W Rejected DMS-archived DSN, 'data set name'`

Explanation: A SAMS:DISK migrated data set was encountered.

Solution: Recall the data set, if desired, and re-submit the job.

`HPS0935I "Base" "Target"`

nr nr Members rejected

nr nr Members selected

nr nr Member name matches

nr nr Synchronized members

nr nr Out of sync members

nr nr Member name mismatches

nr nr Non-orphaned aliases

nr nr Orphaned aliases

`HPS0936W Scratch DSN is already in Superdir: 'dsn'`

`HPS0937I Added to Superdir: ScrDSN = 'dsn'`

`HPS0938W IEBCOPY incompatible member in Dsn: 'dsn'`

Solution: If the reason cannot be determined, contact ChangeMan SSM Technical Support.

`HPS0939I Added to Super Directory: EncDSN = 'dsn'`

`HPS0941I Note:`

SETPRINT parameters "MATCH" and "DSNMATCH" are ignored.

These would have caused conflicts with the "SYNC" and

"DSNSYNC" settings in which the member or data set matching

are the prerequisites.

Solution: Modify the SETPRINT parameters to eliminate the warning message.

`HPS0942I Function REFTARG completed:`

'nr' Datasets Fingerprinted and added to base.

'nr' Datasets were not found, duplicate or err.

`HPS0943I REFTARG has added to base DSN: 'dsn'`

`HPS0944I REFTARG fgp failure`

DSN: 'dsn'

RC= 'nr'

`HPS0945I REFTARG duplicate name rejected DSN: 'dsn`

`HPS0946I REFTARG 'VOLSER' is not the first`

volume of multivolume dataset DSN: 'dsn'

`HPS0947I REFTARG cannot find DSN: 'dsn'`

`HPS0948I LONG DSNbyDSN REPORT - EXCEPTIONSONLY`

Out-of-Sync Data Sets compared:

Base Target S u m m a r y

nnn nnn Member name matches

nnn nnn Synchronized members

nnn nnn Out of sync members

nnn nnn Member name mismatches

nnn nnn Aliases (Non Orphaned)

nnn nnn Orphaned aliases

`HPS0949I Simulation in effect, Finger print tokens 'token' not generated.`

Explanation: Information, finger print token was not generated during this process.

HPS0000-HPS0099

HPS0000I Job Started: 'start time',

HPS0004E Object Master append failure. RC='rc'.

HPS0005E Set group administrator mode failed.

HPS0006E ChangeMan SSM GROUP does not exist.

HPS0007E The Delta Master file could not be opened.

HPS0008E 'DD NAME' is not a valid snapfile. RECFM must be FB and LRECL must be 'num'. Header must be valid.

HPS0009E SET USER failure. RC='rc'.

HPS0010E Object previously defined: Object 'object name'.

HPS0011E OBJVIEW failure. RC='rc', Data set name DSN: 'dsn'.

HPS0012E Rejected command or Syntax error. "value" command "nr"-"nr" Col. "nr".

HPS0013E Syntax error 65. Day-of-month cannot be zero

HPS0014E Memory ptrs not valid. IDVMEMLS=',IDVMEMLS, IDVMEMLA=',IDVMEMLA

HPS0015E No backups found for Member: "member" in Data set DSN: 'dsn'.

HPS0016E 'DD NAME' open failure. R15='nr' Unable to open 'name'

HPS0017E Too much list memory for Member: 'member'.

HPS0018E Backup RC='rc' Member: 'member' Dsn: 'dsn'.

HPS0018I Backup RC='rc' Member: 'member' Dsn: 'dsn'.

HPS0018W Backup RC='rc' Member: 'member' Dsn: 'dsn'.

HPS0019E Recover failed. RC='rc' Member: 'member' Dsn: 'dsn'.

HPS0020E HPSPLIB DD is required. Not found: SYS1.PARMLIB

HPS0021E Backup failed. Member not found: "member" DSN: 'dsn'.

HPS0022E SETCON failure. RC='rc'.

HPS0022I PARMLIB in effect: 'parmlib'

HPS0023E HPSPLIB DD member name not specified.

HPS0024E Open failure of PARMLIB DD 'dismantle'

HPS0025E PARMLIB Dsn is not fixed blocked: 'dsn'

HPS0026E * Error * Site Master 1st record is invalid. Key of record is 'Record key' and length='Record length'

HPS0027E * Error * Site Master record length is invalid. Key of record is 'Record key' and length='Record length'

HPS0028E * Invalid record type 'Record key' in Site Master.

HPS0029I Successful open of Site Master: 'cluster name'

HPS0030E * Error *Site Master record 'Record key' points to a non-existent OM

HPS0031E * Failure of cluster name locate * for cluster 'Cluster name'

HPS0032E * Initialization aborted * R0 = 'content'

HPS0033E Vsam cluster not found in VVDS.

HPS0034I * Site Master remains in sequential mode. *

HPS0035E Record 0 has invalid object count 'number of tracked objects'

HPS0036I Volser = 'volser' Object = 'object name'

HPS0037I M-lrecl = 'size' , M-datsi = 'size' Max-lrec = 'maximum VSAM record size'

HPS0038E Site Master requires conversion.

HPS0039E Site Master and Object Masters are not supported. At least 'site master level' is required. Current version, 'version of the site master'

HPS0039I Override accepted: 'parameter'.

HPS0040E PARMLIB Dsn lrecl is not 80 'dsn'

HPS0041E Invalid parameter “parameter”.

HPS0041W Invalid parameter "parameter"

HPS0042W Parameter is not unique.

HPS0043W Invalid numeric field specified in the override parameter.

HPS0044W Invalid value in the override parameter.

HPS0045E Missing required parameter: "parameter"

HPS0046E DD HPSIN is required.

HPS0047I Object 'zFS filename'.

HPS0048E RTORACCHECK (not recommended) and RTORACFID are mutually exclusive parameters.

HPS0049I *** Master Files Set to Read-Only Mode. ***

HPS0050E ** RLS has prevented access to the Master files. **

HPS0051E Unable to allocate Site Master as defined in HPSPARMS: SITEMASTER 'sitemaster-dsn'.

HPS0052E SSM appears to be active in another screen. Only one instance may be active per ISPF userid.

HPS0053E QUERY error, Return= 'Query Return Code' Reason = 'rc'.

HPS0054I ChangeMan SSM Site Master is in use by: 'enqueue holder'

HPS0100-HPS0199

HPS0100I Dynamic allocation of: 'filename'

HPS0100W ** FAILURE ** DYNAMIC ALLOCATION OF FILE

HPS0101E ** FAILURE ** DYNAMIC ALLOCATION OF VOLUME

HPS0102T 'ACBTYPE' FILE OPENED CLUSTER, 'cluster name'

HPS0103E ** OPEN/CLOSE FAILURE ** ON 'ACB type'

HPS0104E HPSTRACK hh:mm:ss Key = 'key of record'

HPS0105E ** Open Error ** volser, 'volser'

HPS0106E ** OBTAIN ERROR ** VOLSER = 'volser' R15 = 'content'

HPS0107W * I/O read failure on volume 'volser' at CCHH X'cchh'

HPS0108W 'nr' events were lost from following history record.

HPS0109W *** Fingerprint Data Set is empty ***

HPS0110E ** Alloc Failure ** previously allocated volume, 'volser'

HPS0111T Site Master, 'cluster name' -added- key, 'record key'

HPS0112T KEY 'Site Master Key' UPDATED IN THE SITE MASTER FILE, 'ACB cluster name'

HPS0113T KEY 'Site Master Key' ERASED FROM THE SITE MASTER 'ACB cluster name'

HPS0114T KEY 'Object Master Key', ADDED TO THE OBJECT MASTER 'ACBCLUS'

HPS0115T KEY 'Object Master key' UPDATED IN THE OBJECT MASTER 'ACB cluster name'

HPS0116T KEY 'Object Master key' ERASED FROM OBJECT MASTER 'ACB cluster name'

HPS0117W Object Master "name" does not exist.

HPS0118W * REFERRED OBJECT MASTER ALREADY EXISTS * OBJECT MASTER CLUSTER NAME 'cluster'

HPS0119W * Error * OWNER NAME FIELD IS NULL

`HPS0000I Job Started: 'start time',`

`HPS0004E Object Master append failure. RC='rc'.`

`HPS0005E Set group administrator mode failed.`

`HPS0006E ChangeMan SSM GROUP does not exist.`

`HPS0007E The Delta Master file could not be opened.`

`HPS0008E 'DD NAME' is not a valid snapfile. RECFM must be FB and LRECL must be 'num'. Header must be valid.`

`HPS0009E SET USER failure. RC='rc'.`

`HPS0010E Object previously defined: Object 'object name'.`

`HPS0011E OBJVIEW failure. RC='rc', Data set name DSN: 'dsn'.`

`HPS0012E Rejected command or Syntax error. "value" command "nr"-"nr" Col. "nr".`

`HPS0013E Syntax error 65. Day-of-month cannot be zero`

`HPS0014E Memory ptrs not valid. IDVMEMLS=',IDVMEMLS, IDVMEMLA=',IDVMEMLA`

`HPS0015E No backups found for Member: "member" in Data set DSN: 'dsn'.`

`HPS0016E 'DD NAME' open failure. R15='nr' Unable to open 'name'`

`HPS0017E Too much list memory for Member: 'member'.`

`HPS0018E Backup RC='rc' Member: 'member' Dsn: 'dsn'.`

`HPS0018I Backup RC='rc' Member: 'member' Dsn: 'dsn'.`

`HPS0018W Backup RC='rc' Member: 'member' Dsn: 'dsn'.`

`HPS0019E Recover failed. RC='rc' Member: 'member' Dsn: 'dsn'.`

`HPS0020E HPSPLIB DD is required. Not found: SYS1.PARMLIB`

`HPS0021E Backup failed. Member not found: "member" DSN: 'dsn'.`

`HPS0022E SETCON failure. RC='rc'.`

`HPS0022I PARMLIB in effect: 'parmlib'`

`HPS0023E HPSPLIB DD member name not specified.`

`HPS0024E Open failure of PARMLIB DD 'dismantle'`

`HPS0025E PARMLIB Dsn is not fixed blocked: 'dsn'`

`HPS0026E * Error * Site Master 1st record is invalid. Key of record is 'Record key' and length='Record length'`

`HPS0027E * Error * Site Master record length is invalid. Key of record is 'Record key' and length='Record length'`

`HPS0028E * Invalid record type 'Record key' in Site Master.`

`HPS0029I Successful open of Site Master: 'cluster name'`

`HPS0030E * Error *Site Master record 'Record key' points to a non-existent OM`

`HPS0031E * Failure of cluster name locate * for cluster 'Cluster name'`

`HPS0032E * Initialization aborted * R0 = 'content'`

`HPS0033E Vsam cluster not found in VVDS.`

`HPS0034I * Site Master remains in sequential mode. *`

`HPS0035E Record 0 has invalid object count 'number of tracked objects'`

`HPS0036I Volser = 'volser' Object = 'object name'`

`HPS0037I M-lrecl = 'size' , M-datsi = 'size' Max-lrec = 'maximum VSAM record size'`

`HPS0038E Site Master requires conversion.`

`HPS0039E Site Master and Object Masters are not supported. At least 'site master level' is required. Current version, 'version of the site master'`

`HPS0039I Override accepted: 'parameter'.`

`HPS0040E PARMLIB Dsn lrecl is not 80 'dsn'`

`HPS0041E Invalid parameter “parameter”.`

`HPS0041W Invalid parameter "parameter"`

`HPS0042W Parameter is not unique.`

`HPS0043W Invalid numeric field specified in the override parameter.`

`HPS0044W Invalid value in the override parameter.`

`HPS0045E Missing required parameter: "parameter"`

`HPS0046E DD HPSIN is required.`

`HPS0047I Object 'zFS filename'.`

`HPS0048E RTORACCHECK (not recommended) and RTORACFID are mutually exclusive parameters.`

`HPS0049I * Master Files Set to Read-Only Mode. *`

`HPS0050E RLS has prevented access to the Master files. `

`HPS0051E Unable to allocate Site Master as defined in HPSPARMS: SITEMASTER 'sitemaster-dsn'.`

`HPS0052E SSM appears to be active in another screen. Only one instance may be active per ISPF userid.`

`HPS0053E QUERY error, Return= 'Query Return Code' Reason = 'rc'.`

`HPS0054I ChangeMan SSM Site Master is in use by: 'enqueue holder'`

`HPS0100I Dynamic allocation of: 'filename'`

`HPS0100W FAILURE DYNAMIC ALLOCATION OF FILE`

`HPS0101E FAILURE DYNAMIC ALLOCATION OF VOLUME`

`HPS0102T 'ACBTYPE' FILE OPENED CLUSTER, 'cluster name'`

`HPS0103E OPEN/CLOSE FAILURE ON 'ACB type'`

`HPS0104E HPSTRACK hh:mm:ss Key = 'key of record'`

`HPS0105E Open Error volser, 'volser'`

`HPS0106E OBTAIN ERROR VOLSER = 'volser' R15 = 'content'`

`HPS0107W * I/O read failure on volume 'volser' at CCHH X'cchh'`

`HPS0108W 'nr' events were lost from following history record.`

`HPS0109W * Fingerprint Data Set is empty *`

`HPS0110E Alloc Failure previously allocated volume, 'volser'`

`HPS0111T Site Master, 'cluster name' -added- key, 'record key'`

`HPS0112T KEY 'Site Master Key' UPDATED IN THE SITE MASTER FILE, 'ACB cluster name'`

`HPS0113T KEY 'Site Master Key' ERASED FROM THE SITE MASTER 'ACB cluster name'`

`HPS0114T KEY 'Object Master Key', ADDED TO THE OBJECT MASTER 'ACBCLUS'`

`HPS0115T KEY 'Object Master key' UPDATED IN THE OBJECT MASTER 'ACB cluster name'`

`HPS0116T KEY 'Object Master key' ERASED FROM OBJECT MASTER 'ACB cluster name'`

`HPS0117W Object Master "name" does not exist.`

`HPS0118W * REFERRED OBJECT MASTER ALREADY EXISTS * OBJECT MASTER CLUSTER NAME 'cluster'`

`HPS0119W * Error * OWNER NAME FIELD IS NULL`

`HPS0120W * Error * null password field not flagged with "*"`

`HPS0121W * Primary function cannot be selected. Userid is not a primary.`