HPS2100-HPS2199

HPS2101E Object Master is missing.

Solution: Contact ChangeMan SSM Technical Support.

HPS2102I SERNET task (SERH) row: "address"

HPS2103E Module "name" is not from LPA/MLPA library.

Explanation: The intercept modules HPSISTOW, HPSICLOS, HPSIATCH, HPSIBLDL, HPSILINK, HPSILOAD, HPSIXCTL must be loaded from LPA or MLPA during the IPL.

Solution: Rename these modules in the ChangeMan SSM authorized library to prevent them from being loaded from the data set pointed to by the STEPLIB DD.

HPS2104I Module "name" located: "address"

HPS2105E Module "name" not found.

Solution: Contact ChangeMan SSM Technical Support.

HPS2106I SERH field "name": "value".

HPS2107I SERH field "name" "value" changed to "value".

Solution: None. This is part of the dynamic intercept process.

HPS2108I SVC- "code" already intercepted.

Solution: None. It indicates that the RTO has been restarted after an improper or forced shutdown. The previous intercept slots will be re-used. This is normal.

HPS2109E No Objects Defined.

Explanation: The RTO will not start if no objects have been defined for tracking.

Solution: Define an object for tracking, and restart the RTO.

HPS2110I ENQ SVC table resource. rc="code"

Solution: None. It indicates that the RTO has been restarted.

HPS2111I SVC- "code" table entry updated:

Original: "address" "SVC type"

Current: "address" "SVC type"

Solution: None. It shows the original address that the SVC was pointing to, and the new forward address.

HPS2112I DEQ SVC table resource. rc="code"

HPS2113I Quiesce and backout started.

HPS2114W View failed RC= 'nn' Object: 'object name'

HPS2115I SVC-"code" points to "original address"

HPS2116I Backout bypassed.

HPS2117I RTOSYSPRINT= 'echo print' DEBUGG= 'echo debug'

RTOCONSOLE = 'echo wto' TRACE = 'echo trace'

...

HPS2118I DDname = SYSPLEX

Dsname = 'data set name'

Volser = 'volser'

BlkSiz = 'block sixe'

ExtCnt = 'num extents'

TrkCNT = 'num tracks'

HPS2119W DDname = SYSPLEX OPEN failure. Rc= 'nn'

Solution: Verify that the SYSPLEX file exists and has the proper attributes.

HPS2120W DDname = SYSPLEX has more than one extent. File will not be used.

Solution: Re-allocate the SYSPLEX file with a single extent.

HPS2121W DDname = SYSPLEX must have more than one track. File will not be used.

Solution: Re-allocate the SYSPLEX file with one track more than the number of concurrently-active LPARs running the RTO.

HPS2122I SYSPLEX-RTO System is not Activated.

HPS2123I SYSPLEX-RTO System is Activated.

HPS2124W DDname = SYSPLEX All logon slots are taken. Suggest increasing file size.

Solution: Re-allocate the SYSPLEX file with one track more than the number of concurrently-active LPARs running the RTO.

HPS2125I System 'system id' promoted to SYSTEM-n

Explanation: This is due to an RTO being stopped and another moving up in the hierarchy to take its slot.

HPS2126I System 'system id' LPAR-n logon as SYSTEM-n

Explanation: An RTO task has become active within the SYSPLEX system. The "systemid" is the name of the plex in a SYSPLEX environment. The LPAR-n is the nth LPAR that has just started the RTO. For example: System BH3PLEX1 LPAR-01 just started the RTO.

HPS2127I SYSPLEX RTO logons reduced to 'number of logons'

Explanation: An RTO task has been shut down, and was logged off.

HPS2128I Notification System is Activated.

Explanation: The shared memory region is available for the SSMNOTE or SSMMAIL procs.

HPS2129I Waiting for TASK- 'nr' to complete.

HPS2130I TASK- 'nr' detached.

HPS2131I SSMNOTE Info collection started.

HPS2132I Initial Global Processing started.

Explanation: Global Processing is automatically performed when the RTO task is first started unless RTOGLOBE is set to "2".

HPS2133I Initial Global Processing completed.

HPS2134I Member Reference Tracking files:

DDNAME VOLSER DSN

MRTAUX1 'volser' 'dsn'

MRTAUX2 'volser' 'dsn'

MRTAUX1 'volser' 'dsn'

Explanation: Lists the files in use by Member Reference Tracking.

HPS2135E SERNET subsys 'subsys' not found in SSCT.

Explanation: The SERNET started task was unable to add itself to the SSCT. This is most likely an internal SERNET error.

Solution: Contact ChangeMan SSM Technical Support.

HPS2135I Global Capture proceeding . . .

'n' of 'm' objects processed,

last data set completed was: 'object name'

Explanation: The RTO global capture is in progress. 'n' data sets out of the total 'm' data sets defined for tracking have been processed. The last one processed was 'object name'.

HPS2136E SSM subsys list full.

Explanation: The limit of five HPSRTO started tasks on a single LPAR has been reached.

Solution: In general, we recommend a single HPSRTO started task per LPAR.

HPS2137E SSM subsys list error. Retry later.

Explanation: The HPSRTO started task was unable to modify the SSM subsystem list because it was in use by another started task.

Solution: Stop the started tasked, and then restart it.

HPS2138W SVC-'svcnr' intercept in place with no thru address. Intercept skipped.

Explanation: An error has occurred with the ChangeMan SSM SVC intercept processing.

Solution: IPL the system before starting the HPSRTO started task.

HPS2139E Module 'modname' located: PTRMOD is an incompatible version.

Explanation: The intercept module in the LPA library is from an incompatible version of ChangeMan SSM.

Solution: Refresh the LPA library before bringing up the started task.

HPS2140E Thru address in place from incompatible version.

Explanation: Most likely, a prior version of ChangeMan SSM has been brought down, but not all of the SVC intercepts were backed out.

Solution: An IPL is required before starting a newer version of the HPSRTO started task.

HPS2150E Cannot initialize. 08k vector is missing.

Explanation: Unable to initialize ChangeMan SSM.

Solution: Bring down and restart the started task, retry.

HPS2151E Cannot initialize. RC='rc'.

Explanation: This message is issued following a HPS2150E error with a return code of 4.

HPS2152I MRTSWAP received. MRTAUX1/2 file swap completed.

HPS2153E Abend in HPSTASK4, dump was produced.

Explanation: This message is issued by the recovery routine.

Solution: Send dump to ChangeMan SSM Technical Support.

HPS2400-HPS2499

HPS2400E Directory must be empty.

Solution: Correct the error and resubmit.

HPS2401I Supplied FOR value resolves to: 'yyyy/mm/dd_hh:mm:ss'.

HPS2404E Delta Master damage. Type= 'code'

Solution: Contact ChangeMan SSM Technical Support.

HPS2405E Obtain of DD 'dd' Failed with RC='rc'

Solution: Correct the error and resubmit.

HPS2406E DD: 'dd' is not supplied.

Solution: Correct the error and resubmit.

HPS2407E Cannot allocate recall dsn: 'dsn'

Solution: Correct the error and resubmit.

HPS2408I Request to recover 'member' with token 'token' in object 'dsn' is rejected because it is the same as the current member.

HPS2409E Update access denied for restore dsn: 'dsn'

Explanation: The security software prevented the update of the target data set.

Solution: Restore to a different data set, or get update authority for the target data set.

HPS2410E Recall data set is not a pds.

Solution: Correct the error and resubmit.

HPS2411E Output file block size has not been initialized.

Solution: Correct the error and resubmit.

HPS2412E Output file RECFM has not been initialized.

Solution: Correct the error and resubmit.

HPS2413E Recall needs an LRECL at least 'lrecl' but is only 'lrecl'.

Solution: Correct the error and resubmit.

HPS2414E Directory failed to open for pds 'dsn'

Solution: Correct the error and resubmit.

HPS2415E Open failure for pds 'dsn'

Solution: Correct the error and resubmit.

HPS2416E Directory has only 'nr' blocks but needs at least 'nr' blocks.

Solution: Correct the error and resubmit.

HPS2417E Expansion error. Type='code'

Solution: Contact ChangeMan SSM Technical Support.

HPS2418I Member 'member' added to dsn 'dsn'.

HPS2419I Member 'member' replaced in dsn 'dsn'.

HPS2420E Member 'member' failed to stow with rc='rc' parmflag='flag' in dsn 'dsn'

Explanation: The recovery data set does not have enough directory space.

Solution: Exit the SSM ISPF interface, compress the recovery PDS. Or, reallocate the recovery PDS with a larger directory space and retry the function.

HPS2421E Recall needs a blksize of at least 'blksize' but is only 'blksize'

Solution: Correct the error and resubmit.

HPS2422E Load/Object modules can be recovered only to DD SYSUT2

Solution: Specify the recovery PDS on the SYSUT2 DD and resubmit.

HPS2423E PDSE object backups can only be recovered to a PDSE.

Explanation: An attempt was made to recover a PDSE object backup to a non PDSE.

HPS2425I 'member' added to dsn 'data set'.

Explanation: Information only.

HPS2426E 'member' failed to stow with rc= 'rc'

Solution: You have attempted to update a member in a PDSE ...

HPS2500-HPS2599

HPS2501E KEYLEN>250 not supported with AM=FULLTRACK use instead "AM=STANDARD"

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

HPS2502E Cluster not cataloged: 'cluster'

Solution: Correct the error and resubmit.

HPS2503W Cluster 'cluster' is cataloged to volume 'volser'

Solution: Contact ChangeMan SSM Technical Support.

HPS2505W Association error of cluster 'cluster' with data component 'component'

Solution: Contact ChangeMan SSM Technical Support.

HPS2506E VSAM cluster 'cluster' Data component 'component' has an invalid control extension at cchhr 'address'

Solution: Contact ChangeMan SSM Technical Support.

HPS2507E VSAM cluster: "name" Data component: "name" has a missing control extension at cchhr: "value:

Solution: Contact ChangeMan SSM Technical Support

HPS2508E VSAM cluster 'cluster' Data component 'component' has continuation CI required at cchhr 'address'

Solution: Contact ChangeMan SSM Technical Support.

HPS2509E VSAM cluster 'cluster' Data component 'component' continuation CI not expected at cchhr 'address'

Solution: Contact ChangeMan SSM Technical Support.

HPS2510E VSAM cluster 'cluster' Data component 'component' has an invalid control field at cchhr 'address'

Solution: Verify the integrity of the VSAM cluster.

HPS2511E VSAMWORK DD required.

Solution: Correct the error and resubmit.

HPS2512E DD VSAMWORK open failure.

Solution: Correct the error and resubmit.

HPS2513E Sort Volser 'volser' is not online.

Solution: Correct the error and resubmit.

HPS2514E Not a KSDS cluster: 'cluster'

Solution: Verify that the correct VSAM file name was specified.

HPS2515T "nr" Trks/Seg - "value" bytes in sort tree'

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

HPS2516T "value" bytes in merge tree'

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

HPS2529E FGPDD read job file control block failure.

Solution: Verify that FGPDD is specified correctly.

HPS2530E FGP Volser 'VOLSER' is not online.

Solution: Verify that the VOLSER was specified correctly.

HPS2600-HPS2699

HPS2601I RKP= "value" KEYLEN="value" EOF "name"

HPS2602I FGP successfully written to: "name"

HPS2603W Cluster "name" is cataloged to volume "volser"

Explanation: A potential file problem.

Solution: Contact your DASD Administrator or contact ChangeMan SSM Technical Support.

HPS2604E Cluster not found "name"

Solution: Resolve the problem and resubmit the job.

HPS2606E Not a KSDS cluster: "name"

Explanation: Currently, only VSAM KSDS files can be Fingerprinted.