Re: QSECOFR expired, cannot compile

Murphy was an optimist.

Jerry C. Adams
IBM System i Programmer/Analyst
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of John W. Ebrecht
Sent: Monday, July 21, 2008 11:50 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] QSECOFR expired, cannot compile

Murphy's law is alive and well.

On Mon, Jul 21, 2008 at 12:28 PM, Buck <kc2hiz@xxxxxxxxx> wrote:

Justin Taylor wrote:

QSECOFR hit our password expiration interval on Sunday, the same day as

our IPL. The password has been reset now, but I know that some jobs (like
Management Central) failed at IPL due to the expired password.

It almost sounds like a back-end server didn't start. I'd start with
the job log of the submitted job. Set that jobd to log(4 0 *seclvl)
instead of *nolist if needed in order to generate it. If that doesn't
work, try compiling interactively (Remote Systems->Command Execution)
--buck
--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.

--
This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.