Re: CL Program

Best of luck, Troy,

You might review the most frequent messages needing replies;

DSPMSG MSGQ(QSYSOPR) MSGTYPE(*INQ)

and then decide on a default reply for each & add that to the system reply
list entries.

WRKRPYLE

But it wouldn't leave you much to do in the afternoon <g>

Except ...

WRKUSRJOB USER(*ALL) STATUS(*JOBQ) OUTPUT(*) JOBTYPE(*BATCH)  > Jobs stuck
on jobqs
Go SYSTEM > useful menu
DSPJOBLOG > previous commands listing
WRKSBS > processes by subsystem
WRKSYSSTS - system status
WRKSPLF - try the various USRDTA subsets
WRKCFGSTS - connections

When you prompt on a command (F4) you can then press F9 to see extra
parameters.
You can also press F11 to show keywords, or change your profile.
CHGPRF USROPT(*CLKWD *EXPERT *HLPFULL)
If you are taking up CL programming, this is useful.

Do you do any backups ? That can be an interesting area.

As you say, a job's a job.
Hang in there, & do give menus a try.

Fiona
fiona.fitzgerald@notes.royalsun.com