Hi lizette,

For all the zos mounts, I use my service mount batch job as the template for 
those in parmlib with modifications to syntaxes to fit.  Everything else for 
/tmp, ,etc, dev, and any other ancillary vendor, user file systems are 
ieheyeball.   There aren't many that would fail an ipl entirely so can be fixed 
after you are up.  There is the health check that was mentioned,  but that only 
calls out differences between what is in parmlib and what is actually mounted.

Hope this helps!
________________________________
From: IBM Mainframe Discussion List <[email protected]> on behalf of 
Lizette Koehler <[email protected]>
Sent: Sunday, January 24, 2021 1:14:28 AM
To: [email protected] <[email protected]>
Subject: How to validate mount points for IPLs

**CAUTION EXTERNAL EMAIL**

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails**

List



I am not quite sure what technique or process I can put together to validate
the Mount points in BPXPRMxx prior to an IPL



SYNTAXCHECK only makes sure that I did not finger check



It does not say this will mount or not mount



And with z/OS and other products using lots of mount points - hand checking
is getting difficult.



Any ideas are welcomed.



Thank you



Lizette




----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
**CAUTION EXTERNAL EMAIL**

**DO NOT open attachments or click on links from unknown senders or unexpected 
emails**



${If.App.WXP}Classification: Internal Use${If.End}
This e-mail transmission contains information that is confidential and may be 
privileged.
It is intended only for the addressee(s) named above. If you receive this 
e-mail in error,
please do not read, copy or disseminate it in any manner.  If you are not the 
intended 
recipient, any disclosure, copying, distribution or use of the contents of this 
information
is prohibited. Please reply to the message immediately by informing the sender 
that the 
message was misdirected. After replying, please erase it from your computer 
system. Your 
assistance in correcting this error is appreciated.




----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to