Re: F9 retrieve stopped working

On 18-Mar-2015 12:34 -0500, Jack Tucky wrote:

F9 retrieve doesn't work anymore. Is it related to the job
description settings?

I'll type DSPPFM FILE, hit enter, F9 will bring something previous to
that up.

I don't know if it's related but we did some job description changes
to handle moving some libraries to an iASP. I checked other job
descriptions on other systems and the logging matches. Here is what I
have:

Message logging:
Level . . . . . . . . . . . . . . . . . . . . : 4
Severity . . . . . . . . . . . . . . . . . . . : 0
Text . . . . . . . . . . . . . . . . . . . . . : *NOLIST
Log CL program commands . . . . . . . . . . . . : *YES

Any ideas?

Issuing the command at the "Command Entry" for the QCMD shell? After F11=Display Partial if using the "Display Full" version, does F10=Include Detailed Messages show the prior request message(s); the message that is not retrieved by F9=Retrieve?

Look at the WRKJOB OPTION(*DFNA) for the "Level" of the "Message logging", not in a Job Description (JOBD). What is defined for those attributes in the *JOBD object are irrelevant to those attributes for the active job, except for what might have been initially established; those attributes could have been changed anytime since the initiation of the job.

If the active LOG() setting matches what is shown in the quoted message, then a feature may be deleting the request message; a Trace covering the request, returning from the request, and then pressing F9 should reveal what asks to delete the request if not merely suppressed due to either the Level<=1 or the Level=2 and the error was suppressed due to the message Severity Code (SEV) not exceeding the Severity of the LOG() attributes.