ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Panvalet PAM module

book

Article ID: 51354

calendar_today

Updated On:

Products

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

Issue/Introduction

Description:

After upgrading Panvalet 14.5 from SP00 to SP01 we relinked the PAM module, do we need to relink it again when do a z/OS upgrade?

Solution:

No, it should not need to be re-linked for a z/OS upgrade. It only needs to be re-linked 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