I agree with the others .. Profiles used exclusively for batch
processing shouldn't be getting disabled unless someone is mis-using
them or you have some external process that's disabling them [like
That said there are workarounds. A band aid would be to have your batch
PGM call a PGM that adopts authority to a SECADM-level account and does
a CHGUSRPRF XXXXX STATUS(*ENABLED) PASSWORD(YYYYY) before the profile is
needed. Or put that code in some PGM that runs each day.
But the real fix is to find what's disabling the profile and take care
of that. For instance, with the ANZDFTPWD command you can create a list
of profiles for the command to ignore. Or, if you see invalid signon
attempts for the profile, track down who is trying to use the batch
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.