Thanks. I just checked the logs from all three systems for that day. No $HASP263 messages were issued on any system.
Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get&[email protected] ------- Original Message ------- On Tuesday, March 22nd, 2022 at 5:59 PM, Feller, Paul <[email protected]> wrote: > Mark, I guess I would ask if you saw any $HASP263 messages on the other > lpars? Seeing message $HASP263 would indicate issues with the checkpoint > processing. That could hold up things on the other members in the MAS. > > From the JES2 message manual for z/OS 2.4. > > $HASP263 > > Explanation > > WAITING FOR ACCESS TO JES2 CHECKPOINT VOLUME volser > > LOCK HELD BY MEMBER member_name > > LOCK HELD BY SYSTEM > > SYSTEM MANAGED PROCESS ACTIVE > > When the primary checkpoint data set resides on DASD, JES2 has issued a > RESERVE operation to the CKPT1 or > > CKPT2 data set on volume volser. The number of seconds specified as the time > interval on the LOCKOUT > > parameter on the MASDEF initialization statement or on the $T MASDEF operator > command has elapsed, but the > > RESERVE operation has not completed. Another member in the multi-access spool > configuration might have > > ended while holding the hardware RESERVE on the checkpoint data set. > > This message is informational and displays why the lock cannot be obtained. > Either: > > • The lock is held by another member of the MAS. > > • The lock is in transition and is held by MVS. If this state persists, there > might be an XCF signaling problem or a system might have failed. > > • The lock cannot be obtained because a system managed process is active for > the structure. > > Paul Feller > > GTS Mainframe Technical Support > > -----Original Message----- > > From: IBM Mainframe Discussion List [email protected] On Behalf Of > Mark Jacobs > > Sent: Tuesday, March 22, 2022 4:25 PM > > To: [email protected] > > Subject: JES2 Purge Processing [EXTERNAL] > > Yesterday we had a job with a huge amount of output take about 48 minutes to > complete purge processing. While it was being purged everything else on that > system that required JES2 services, basically spool space, wasn't able to do > so and was waiting for the purge to complete. This is a 3 system MAS, and I > think it's safe to say that any JES2 tuning activities hasn't been done in a > very long time. > > Does anyone have suggestions on what to look at in the system/JES2PARM > configuration that might speed purge processing up if this problem occurs > again? > > Mark Jacobs > > Sent from ProtonMail, Swiss-based encrypted email. > > GPG Public Key - > https://urldefense.proofpoint.com/v2/url?u=https-3A__api.protonmail.ch_pks_lookup-3Fop-3Dget-26search-3Dmarkjacobs-40protonmail.com&d=DwIGaQ&c=9g4MJkl2VjLjS6R4ei18BA&r=eUhu3PeeWy6RTndlJVKembFjFsvwCa8eeU_gm45NyOc&m=fxAqxmkYZvk6cRaMRvdn973XKmXJectUWeVC64AT8M4YsiucmroOptanei41wdqL&s=mX7vghlPjDzvU7u_YjjvHEluDHIww2MgJmcgmon4aKg&e= > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > > Please note: This message originated outside your organization. Please use > caution when opening links or attachments. > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
