Relinking PAM when upgrading z/OS operating system.

book

Article ID: 52917

calendar_today

Updated On:

Products

CA Database Analyzer (IMS Tools) CA Mainframe Configuration Manager for IMS for z/OS IMS TOOLS - MISC CA Compress Data Compression (IMS Tools) CA Database Analyzer for IMS for z/OS CA Database Copier for IMS for z/OS CA Database Organizer for IMS for z/OS CA Mainframe Extended Terminal Manager (IMS Tools) CA High Performance Recovery for IMS for z/OS CA Database Organizer (IMS Tools) CA Mainframe Program Restart Manager for IMS for z/OS CA Secondary Index Builder for IMS for z/OS CA Secondary Index for IMS for z/OS CA JARS CA JARS Resource Accounting CA JARS SMF Director CA JMR CA MIM Resource Sharing (MIM) CA MIM Data Sharing (MII) CA MIM Tape Sharing (MIA) CA MIM Message Sharing (MIC) MIM BASE Nastel AutoPilot for WebSphere MQ CA PanApt CA PanAudit CA Panvalet CA QuickFetch CA Raps VSE CA Scheduler VSE CA SMR CA SOLVE:Operations Automation SOLVE:Access Session Management CA SOLVE:CA Mainframe Connector CA SOLVE:FTS CA SYSVIEW Performance Management NXBRIDGE - SYSYVIEW/ENDEVOR CA 2E CA SOLVE

Issue/Introduction

Description:

We upgraded Panvalet to 14.5 SP01 and relinked PAM. Do we need to relink PAM again when we upgrade to z/OS 1.11?

Solution:

No, it should not need to be relinked for a z/OS upgrade. It only needs to be relinked when doing a Panvalet Release or SP upgrade and/or when any apply of maintenance hits PAM. The best way is to not statically link PAM in user programs and do the proper dynamic calls to PAM instead in the user program.

Environment

Release:
Component: C21E