Is there any maintenance required for CA PanExec 5.3 when defining UCBs above the 16 bit line?
search cancel

Is there any maintenance required for CA PanExec 5.3 when defining UCBs above the 16 bit line?

book

Article ID: 23674

calendar_today

Updated On:

Products

Panvalet

Issue/Introduction

 

 Is there any maintenance required for CA Panexec 5.3 to use UCBs defined above the 16 bit line.

 

 

Environment

Release: PEXEC.00200-5.3-Panexec
Component:

Resolution

Scenario 1 is for when you have not IPLed yet with UCBs above the 16 bit line and scenario 2 is for when you have already IPLed with them and PanExec loader is failing to initialize, usually with S0C4 abend.

Scenario 1.

Download fix TF4E045 from CA Support Online. Follow the instructions in the text portion of the fix to apply it the normal way when PanExec is running.

 

Scenario 2.

If CA PanExec loader will not initialize (usually due to S0C4 abends) then you cannot apply fix TF4E045 the normal way.

There are several alternative methods:

  1. Do a new install of Ca Panexec at SP2 specifying non-active PanExec.

  2. Remove UCBs above the line temporarily, start CA PanExec and install TF4E045.

  3. Install the fix on a different working PanExec system updating the CAILIB/PANELOAD that will be used on the failing system.

  4. Linkedit the modules introduced by TF4E045 outside of PanExec. The following steps will accomplish this:

    1. Download TF4E045 from Support Connect and binary transfer to a sequential file on your mainframe. DCB should be FB LRECL=80

    2. Create a PDS named PANEXEC.TF4E045.OBJLIB that will contain 4 members. DCB should be RECFM=FB, LRECL=80, BLKSIZE=3120. Do not exceed BLKSIZE=3120. Copy records from the sequential file to the members starting with .ESD and ending with the following .END. The member name is in each .ESD record starting in column 17. The 4 members are: L10I236, XPEL037, XPEO037 and XPEO005. Be sure not to copy any of the comments or JCL before the first .ESD or after the last .END record.

    3. Take a copy of your named CURRENT.PEX.CAILIB/PANELOAD into a library named TEST.WORK.PEX.CAILIB/PANELOAD.

    4. Execute the following linkedit JOBs to relink PANCMP53 and PANERENT:
      //JOBCARD
      //*
      //LK1 EXEC PGM=IEWL,PARM='LIST,XREF,MAP'
      //SYSOUT DD SYSOUT=*
      //SYSPRINT DD SYSOUT=*
      //SYSLIN DD DDNAME=SYSIN
      //SYSLMOD DD DSN=TEST.WORK.PEX.CAILIB/PANELOAD,DISP=SHR
      //SYSLIB DD DSN=CURRENT.PEX.CAILIB/PANELOAD,DISP=SHR
      //OBJLIB DD DSN=PANEXEC.TF4E045.OBJLIB,DISP=SHR
      //SYSUT1 DD UNIT=VIO
      //SYSIN DD * INCLUDE OBJLIB(XPEL037)
      IDENTIFY XPEL037('* TF4E045-XPEL037-PANEXEC-0539606 *')
      INCLUDE OBJLIB(XPEO005)
      IDENTIFY XPEO005('* TF4E045-XPEO005-PANEXEC-0539606 *')
      INCLUDE SYSLIB(PANCPM53)
      MODE AMODE(24),RMODE(24) ENTRY XPEPANCP
      NAME PANCPM53(R)
      //
      //JOBCARD
      //*
      //LK2 EXEC PGM=IEWL,PARM='LIST,XREF,MAP'
      //SYSOUT DD SYSOUT=*
      //SYSPRINT DD SYSOUT=*
      //SYSLIN DD DDNAME=SYSIN
      //SYSLMOD DD DSN=TEST.WORK.PEX.CAILIB/PANELOAD,DISP=SHR
      //SYSLIB DD DSN=CURRENT.PEX.CAILIB/PANELOAD,DISP=SHR
      //OBJLIB DD DSN=PANEXEC.TF4E045.OBJLIB,DISP=SHR
      //SYSUT1 DD UNIT=VIO
      //SYSIN DD *
      INCLUDE OBJLIB(XPEO037)
      IDENTIFY XPEO037('* TF4E045-XPEO037-PANEXEC-0539606 *')
      INCLUDE OBJLIB(XPEO005)
      IDENTIFY XPEO005('* TF4E045-XPEO005-PANEXEC-0539606 *')
      INCLUDE SYSLIB(PANERENT)
      MODE AMODE(24),RMODE(24)
      ENTRY XPEO043
      NAME PANERENT(R)
      //
    5. Start PanExec loader using the SYSLMOD library TEST.WORK.PEX.CAILIB/PANELOAD

    6. Reapply TF4E045 the correct way, you will need to STEPLIB to NEW PANERENT in PGM=PANEXEC job, the PANESRL must contain changed code for proper Panexec Maintenance going forward.