RE: BRMS logging difference between full nightly save and dedicted system save

I found the issue.

AJS uses the jobd of the user specified for the job, it doesn't use the jobd.
My two saves did have a different user, which I initially overlooked.

Issue resolved.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Jack Kingsley
Sent: Friday, January 25, 2019 5:18 AM
To: Midrange Systems Technical Discussion
Subject: Re: BRMS logging difference between full nightly save and dedicted system save

Paul, if you look at the entry defined in AJS, what are the values for
jobd. Is it using hard coded job descriptions or *USRPRF or *JOBCTL.

On Thu, Jan 24, 2019 at 4:54 PM Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
wrote:

I'm seeing a logging difference between my BRMS full nightly save and my
BRMS dedicated system save.
Both jobs submitted via AJS,
same user,
same jobd.

Jobd logging is set:
Message logging:
Level . . . . . . . . . . . . . . . . . . . . : 4
Severity . . . . . . . . . . . . . . . . . . . : 0
Text . . . . . . . . . . . . . . . . . . . . . : *SECLVL
Log CL program commands . . . . . . . . . . . . : *YES

The full nightly save logs per the jobd, *SECLVL.
The system save logging is *MSG.

This may seem minor, but *SECLVL gives important extra detail which is
very useful for recovery/migration.
My system save, which I will use for the migration, is missing this detail.

Any one from the group know what might be changing this and how to correct
the logging.


Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx
http://www.pencor.com/
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com