Re: F9 retrieve stopped working

I don't think job descriptions have any bearing on how F9 retrieve works.

If the "DSPPFM FILE" (or whatever command entered) fails, the command line
keeps the failed command; if you F9 from that point, you will get the
command entered previous to that command.

Also, I presume you are experiencing this from a bonafide system command
line, and not within some third-party app's custom menu program, for which
the F9 retrieve may be a configurable option.

Finally, ditto what Scott said. There are any number of Windows apps that
can cause conflicts with F-keys, although I'm not sure how they would cause
a command prior to the most recent one to display after one F9 hit.

- Dan

On Wed, Mar 18, 2015 at 1:34 PM, Jack Tucky <jacktucky@xxxxxxxxx> 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?

Thanks, Jack