HPS3000-HPS3099
HPS3000E      No Object Master is appended to system.
Solution: Contact ChangeMan SSM Technical Support.
HPS3000I      Member Reference Tracking started.
HPS3001E      Multiple Object Master appended to system.
Solution: Contact ChangeMan SSM Technical Support.
HPS3001I      *Rejected* HSM migrated data set: 'DSN'
HPS3002I      *Rejected* DMS migrated data set: 'DSN' message.
HPS3002T      Scheduled to be erased. Key: "value"
Explanation: This is a trace (or logging) message.
HPS3003I *Rejected* Multi-volume d/s support in batch only
HPS3003T Scheduled to be erased. Key: "value"
Explanation: This is a trace (or logging) message.
HPS3004I      DSN Fingerprinted and added to Base: 'DSN'
HPS3005I      'nr' records in Object Master.
HPS3006I      'nr' records in Delta Master.
HPS3007T      Scheduled to be erased. Key: "value"
Explanation: This is a trace (or logging) message.
HPS3008T      Site Master key updated: "value"
Explanation: This is a trace (or logging) message.
HPS3009T      Site Master key removed: "value"
Explanation: This is a trace (or logging) message.
HPS3010T      Site Master key added: "value"
Explanation: This is a trace (or logging) message.
HPS3011T      Object Master key added: "value"
Explanation: This is a trace (or logging) message.
HPS3012T      Object Master key removed: "value"
Explanation: This is a trace (or logging) message.
HPS3013T      Delta Master key removed: "value"
Explanation: This is a trace (or logging) message.
HPS3014T      Delta Master key updated: "value"
Explanation: This is a trace (or logging) message.
HPS3015I      Action summary:
HPS3031I      'nr' records in Site Master.
HPS3099I      Mask used: 'DSN'.
Explanation: A mask was used during fingerprinting of this data set.
HPS3100-HPS3199
HPS3100W      ** Failure ** Dynamic allocation of file: 'data set name' SVC99 error field = 'hhhhhhhh' info = 'hhhhhhhh'
Solution: Determine the cause of the allocation failure.
HPS3107W      * I/O read failure on volume 'volser' at CCHH 'REFCCHH'
Solution: Determine the cause of the I/O read failure.
HPS3108W      Not Quiescent! Cluster: 'cluster name'
Explanation: Some activity was detected on the cluster during the backup operation. Updates occurring during the backup may not be detected until the next backup.
HPS3109W      Not Quiescent! Cluster: 'cluster name' CA split has occurred during backup.
Explanation: A CA split was detected on the cluster during the backup operation.
Solution: Re-run the job when the cluster has less activity.
HPS3113E      'variable message text'
Explanation: The first line of the message depends on the reason code in the Reason field.
Reason code 20 displays "0 index records were read"
Reason code 21 displays "CA size cannot be zero"
HPS3200-HPS3299
HPS3200I      'nr' DSNs 'nr' Clusters on Volser 'VOLSER'
HPS3201I      'nr' DSNs 'nr' Clusters on 'nr' Volumes
HPS3202I      'nr' members in 'nr' data sets.
HPS3220E      Read job file control block failure. RC='rc' DDNAME: 'out dd'
Solution: Verify that the DD is present.
HPS3300-HPS3399
HPS3300W      Open failure for Basket data set. DSname=DSN DDname=DDNAME
Solution: Verify that the correct DSN or DD name is specified.
HPS3301W      Empty Basket Data Set. DSname=DSN DDname=DDNAME
Solution: Verify that the correct DSN or DD name is specified.
HPS3302W      Close failure on basket data set.
Solution: Resubmit the job.
HPS3303I      Input file attributes:
HPS3304E      Basket file is not RECFM=U,BLKSIZE=4096.
Explanation: The Basket file specified has the wrong RECFM; it is not a Basket file.
Solution: Correct the Basket file reference and resubmit the job.
HPS3305W      A record segment has a length of nr bytes.
Solution: Correct the data set or remove it from the process.
HPS3306W      A physical record exceeds its length indicator.
Solution: Correct the data set or remove it from the process.
HPS3307W      Physical EOF reached but not Logical EOF.
Explanation: The Basket file may be damaged.
Solution: Verify that the Basket file was created and transferred successfully.
HPS3308E      File is neither a Basket nor a Reverse Basket.
Explanation: The Basket file was not specified correctly.
Solution: Verify that the Basket DSN is correctly specified.
HPS3309E      zFS Basket file is not RECFM=U,BLKSIZE=4096.
Explanation: The zFS Basket file specified has the wrong RECFM; it is not a zFS Basket file.
Solution: Correct the zFS Basket file reference and resubmit the job.
HPS3332I      S U M M A R Y :
HPS3600-HPS3699
HPS3601I      LOAD FGP: 'dsn'
HPS3602I      zFS file comparison report summary
HPS3603I      zFS Change Basket import summary
HPS3604E      Error closing change basket data set
Solution: Contact ChangeMan SSM Technical Support.
HPS3605W      zFS Change Basket is empty or damaged
Solution: Recreate the change basket and retry the function.
HPS3606I     Change Basket data set created successfully.
HPS3607I      Export to zFS Change Basket:
HPS3608I      Export to Reverse zFS Change Basket:
HPS3609W      Basket data set is empty:
Solution: Recreate the change basket and retry the function.
HPS3610W      Error closing basket data set:
Explanation: The basket data set did not close correctly. The comment text is the text entered in the Basket Comment field on the Package Changes panel (Detection & Synchronization).
Solution: Note the Comment text and contact ChangeMan SSM Technical Support.
HPS3613E      zFS Error, Return Code:'register 15 contents'
Explanation: There was an error processing zFS files. The Return Code specifies the contents of register 15.
Solution: Note the Return Code and contact ChangeMan SSM Technical Support.
HPS3613W      zFS Error, Return Code:'register 15 contents'
Explanation: There was an error processing zFS files. The Return Code specifies the contents of register 15.
Solution: Note the Return Code and contact ChangeMan SSM Technical Support.
HPS3614E      Cannot create file, directory does not exist. Use the FORCE parameter, or create the missing directory.
Explanation: The specified directory does not exist, so the file cannot be created.
Solution: Use the FORCE parameter to create the file, or create the missing directory and then create the file.
HPS3614W      Directory does not exist, creating:
Explanation: The specified directory does not exist and is being created.
Solution: This is a warning message indicating that a new path and file are being created; no user action is required.
HPS3615W      Character Special files are not supported: 'directory/filename'
Explanation: The displayed filename will be skipped during fingerprinting.
Solution: This is a warning message indicating that a file will not be processed. To prevent the warning message from being issued, exclude the displayed filename.
HPS3616W      FIFO (named pipe) files are not supported: 'directory/filename'
Explanation: The displayed filename will be skipped during fingerprinting.
Solution: This is a warning message indicating that a file will not be processed. To prevent the warning message from being issued, exclude the displayed filename.
HPS3617W      Block Special files are not supported:
Explanation: The displayed filename will be skipped during fingerprinting.
Solution: This is a warning message indicating that a file will not be processed. To prevent the warning message from being issued, exclude the displayed filename.
HPS3618W      Socket files are not supported:
Explanation: The displayed filename will be skipped during fingerprinting.
Solution: This is a warning message indicating that a file will not be processed. To prevent the warning message from being issued, exclude the displayed filename.
HPS3619W      Error listing directory: R15=nnn
Explanation: The displayed directory will be skipped during fingerprinting. The return code is in register 15 (R15=nnn).
Solution: This is a warning message indicating that a directory will not be processed. To include the directory, give the user READ access to the directory. For more information, refer to the IBM manual z/OS UNIX System Services User's Guide, in the section “Handling Security for Your Files”.
HPS3620W      Directory not found. Check specification and case.
Explanation: The displayed directory will be skipped during fingerprinting.
Solution: This is a warning message indicating that a directory cannot be found. Verify that the directory specification is correct (it is case-sensitive), and that it exists.
HPS3621E      zFS Basket Dsn: 'dsn' is not dsorg=PS,recfm=FB.
Explanation: The specified data set does not have the correct data set organization and record format for an zFS Basket data set.
Solution: Verify that the correct data set name (dsn) has been being specified.
HPS3622E      zFS Basket Dsn: 'dsn' is not a Basket file.
Explanation: The specified data set is not a valid zFS Basket data set.
Solution: Verify that the correct data set name (dsn) has been being specified.
HPS3623E      zFS Fingerprint Dsn: 'dsn' is not dsorg=PS,recfm=FB.
Explanation: The specified data set does not have the correct data set organization and record format for an zFS Fingerprint data set.
Solution: Verify that the correct data set name (dsn) has been being specified.
HPS3624E      zFS Fingerprint Dsn: 'dsn' is not a Fingerprint file.
Explanation: The specified data set is not a valid zFS Fingerprint data set.
Solution: Verify that the correct data set name (dsn) has been being specified.
HPS3636I      Fingerprint data set created successfully
Explanation: The Fingerprint data set has been successfully created.
Solution: This is an informational message; no user action is required.
HPS3642I      Fingerprint data set loaded successfully.
Explanation: The Fingerprint data set has been successfully loaded.
Solution: This is an informational message; no user action is required.
HPS3651W      Fingerprint data set is damaged, empty, or had
Explanation: The Fingerprint data set is not usable.
Solution: Change the specified INCLUDE or EXCLUDE mask(s) to ensure that at least one file is included. If no masks were used, recreate the fingerprint data set and retry the function.
HPS3680I      File(s) added to 'base/targ'
Explanation: One or more files have been added as specified.
Solution: This is an informational message; no user action is required.
HPS3901I      HPSISTOW Protected member 'name' cannot be [added/updated/deleted/ renamed].
Explanation: The displayed MLS-protected member name cannot be added, updated, deleted, or renamed. The MLSABEND parameter of HPSPARMS determines if an ABEND will occur. MLSABEND YES will cause a User ABEND U913-38. MLSABEND NO will result in a return code of 16, reason code 52, but the job will not ABEND.
Solution: This is an informational message; no user action is required.
HPS4000-HPS4099
HPS4001E      ChangeMan SSM Synchronization Components not licensed.
Explanation: The Synchronization Components of ChangeMan SSM has not been licensed.
Solution: Contact ChangeMan SSM Technical Support.
HPS4002E      ChangeMan SSM Change Tracking Component has not been licensed.
Explanation: The Change Tracking Component of ChangeMan SSM has not been licensed.
Solution: Contact ChangeMan SSM Technical Support.
HPS4003E      ChangeMan SSM Change Detection Component is not licensed.
Explanation: The Change Detection Component of ChangeMan SSM has not been licensed.
Solution: Contact ChangeMan SSM Technical Support.