ICPSMSGS59 - INTERR: Internal error locating PSS main control block
Article ID: 93275
Updated On:
Products
Ideal
Issue/Introduction
After upgrading Ideal to 15.1 from 14.0 I am getting error:
ICPSMSGS59 - INTERR: Internal error locating PSS main control block
ICPSMSGS59 - INTERR: Internal error locating PSS main control block
Environment
z/os, CA IPC 15.1
Cause
ICPSMSGS59 - INTERR: Internal error locating PSS main control block
Reason:
An internal error occurred during initialization of the PSS main control block in session storage.
Possible reasons are:
■ Permanent storage could not be allocated.
■ The panel library could not be initialized.
■ The PSS#OPTIONS member could not be read from the panel library.
■ SCPSV#R# could not be loaded.
■ The spool could not be initialized.
■ The PSS Directory member could not be opened.
Action:Make sure the following conditions are met:
■ The panel library is defined to the system and is properly formatted.
■ The PSS#OPTIONS member exists in the panel library.
■ The load module SCPSV#R# exists.
■ The spool was created and is properly formatted.
If the above conditions are met and the error recurs and if you are in CA Ideal, enter DISPLAY ERROR (DIS ERR) in the command area. Otherwise, enter DIS INTERR. Record all information displayed and report this problem to CA Ideal Technical Support.
Reason:
An internal error occurred during initialization of the PSS main control block in session storage.
Possible reasons are:
■ Permanent storage could not be allocated.
■ The panel library could not be initialized.
■ The PSS#OPTIONS member could not be read from the panel library.
■ SCPSV#R# could not be loaded.
■ The spool could not be initialized.
■ The PSS Directory member could not be opened.
Action:Make sure the following conditions are met:
■ The panel library is defined to the system and is properly formatted.
■ The PSS#OPTIONS member exists in the panel library.
■ The load module SCPSV#R# exists.
■ The spool was created and is properly formatted.
If the above conditions are met and the error recurs and if you are in CA Ideal, enter DISPLAY ERROR (DIS ERR) in the command area. Otherwise, enter DIS INTERR. Record all information displayed and report this problem to CA Ideal Technical Support.
Resolution
Site having that problem generally format and reinitialize ADROUT file.
Conditions related to the spool as mentioned above.
In IPC 15.1 this is done at upgrade time via job CAVQSAMP(VQUPG01).
Or it can be done via the JCL below:
//FORMAT EXEC PGM=VLSUTIL To format the new ADROUT
//STEPLIB DD DSN=....IPC15.x...CAVQLOAD,DISP=SHR
//* with CUSLIB
//VLSFILE DD DSN=.....ADROUT,DISP=SHR
//AUXPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
FORMAT BLKSIZE=4000,NAMELEN=11
LIBRARY
/*
//PSSUTIL EXEC PGM=SCPSUTIL to initialize the new ADROUT Directory
//STEPLIB DD DSN=....IPC15.x....CAVQLOAD,DISP=SHR
//* with CUSLIB
//ADRPNL DD DSN=......ADRPNL,DISP=SHR
//ADROUT DD DSN=......ADROUT,DISP=SHR
//AUXPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
INIT
//
Conditions related to the spool as mentioned above.
In IPC 15.1 this is done at upgrade time via job CAVQSAMP(VQUPG01).
Or it can be done via the JCL below:
//FORMAT EXEC PGM=VLSUTIL To format the new ADROUT
//STEPLIB DD DSN=....IPC15.x...CAVQLOAD,DISP=SHR
//* with CUSLIB
//VLSFILE DD DSN=.....ADROUT,DISP=SHR
//AUXPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
FORMAT BLKSIZE=4000,NAMELEN=11
LIBRARY
/*
//PSSUTIL EXEC PGM=SCPSUTIL to initialize the new ADROUT Directory
//STEPLIB DD DSN=....IPC15.x....CAVQLOAD,DISP=SHR
//* with CUSLIB
//ADRPNL DD DSN=......ADRPNL,DISP=SHR
//ADROUT DD DSN=......ADROUT,DISP=SHR
//AUXPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
INIT
//
Additional Information
If the condition is due to ADROUT being Full:
- You could also run SCPSUTIL with the LIBRARY function to list the contents.
Then run SCPSUTIL again with DELETE filename filenumber
You can only delete one report at a time in this way.
- If it about reports not being deleted? You should check the RETENTION value in SET OUT SITE options,
maybe you need to set a shorter retention period.
See:
https://docops.ca.com/ca-datacom-tools/15-1/en/using-inter-product-components-ipc/configuring-ca-ipc/customizing-the-print-subsystem-component/pss-recovery-and-multiple-cics-environments
- You could also run SCPSUTIL with the LIBRARY function to list the contents.
Then run SCPSUTIL again with DELETE filename filenumber
You can only delete one report at a time in this way.
- If it about reports not being deleted? You should check the RETENTION value in SET OUT SITE options,
maybe you need to set a shorter retention period.
See:
https://docops.ca.com/ca-datacom-tools/15-1/en/using-inter-product-components-ipc/configuring-ca-ipc/customizing-the-print-subsystem-component/pss-recovery-and-multiple-cics-environments
Feedback
Yes
No
Powered by
