As Jim stated, probably the logging level of the jobd.
However, I've also seen 3rd party apps code a CHGJOB LOG(4 00 *NOLIST) LOGCLPGM(*NO) in their initialization routine, thus overriding the jobd settings.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Thursday, January 19, 2017 1:10 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Never seen this before: F9 doesn't recall commands, and they don't appear in the joblog
Logging level on the job is the cause. Most likely the job description from your vendor specifies no logging in which case they are doing it to you.
If it's your job description then it's a self-inflicted wound. Change the job description so that logging starts and all should be well.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Tammy Scott
Sent: Thursday, January 19, 2017 12:06 PM
To: Midrange Systems Technical Discussion
Subject: RE: Never seen this before: F9 doesn't recall commands, and they don't appear in the joblog
We have a 3rd party software and every time I go to their menus, it does
this to me. The Vendor says they do not do this...but, they do. Happens
to my co-worker too.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Thursday, January 19, 2017 11:38 AM
To: Midrange Systems Technical Discussion
Subject: Never seen this before: F9 doesn't recall commands, and they don't appear in the joblog
I just noticed that on a terminal session with one of our customers, the commands I enter don't appear in the joblog, and can't be recalled with F9.
I've never seen this before, anywhere, in over 2 decades futzing around with AS/400s. Can somebody explain? Is it something to do with the job's message logging setting? Is it something I can change at the user profile level?
--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://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:
http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://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:
http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://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:
http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.