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.



Article ID: 51855


Updated On:


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



We have the value UPTIMEST=N in our SYS1.PARMLIB(PANSYS01). With that being the case, what would cause different values in the LACCESS value versus the LMAINT value?


Any READ attempt from PVISPF, PANTSO, or Panvalet Batch(PAN#?) jobs will update the LAST ACCESS date.

The UPTIMEST=N will prevent the update of the access date for every access of a member by the Panvalet Subsystem.

The value of N corresponds to a universal specification of the OPEN=INP parm(read-only access) used in batch jobs.


Component: C21E