Subject: [SYS21] RE: development environment

["Brunk, Kevin" <Kevin.Brunk@xxxxxxxxxxxx>]

When I try to run WRKSYSACT on our 730 @ V4R5, I get the message "Command 
WRKSYSACT in library *LIBL not found".  I then did a DSPOBJD *ALL/WRKSYSACT 
*CMD to see if the command was even on our system. It was in the previous 
version libraries QSYSV3R2M0, QSYSV4R2M0, QSYSV4R3M0, QSYSV4R4M0.  I added 
QSYSV4R4M0 to my library list and tried it again, getting the message: "Command 
WRKSYSACT not valid for current release."  Sooooo - it looks like this is a 
retired command and like old soldiers, OS/400 commands don't die, they just 
fade away!

Regarding programmer "sins", it's true programmers can affect performance of 
"production" work by doing development on a production machine.  But, 
sometimes, a production machine is your only development choice.  Good 
programmers are aware of this and their concern for inconveniencing their 
"customers" should lead them to use performance-friendly practices like:
        * always submit create functions (CRTRPGPGM, CRTPF, CRTLF, etc.) to 
batch.
      * don't build new logical files during normal work hours (remember, you 
don't actually need a member in the file just to compile the program - i.e. 
CRTLF MBR(*NONE) if all you need to do is compile).
      * don't use RUNQRY interactively.
      * if using the console for development (bad idea to start with), CHGJOB 
RUNPTY(20).
      * if using the console for any long running task (bad idea to start 
with), CHGJOB RUNPTY(50).
      * if debugging a "batch" like process interactively, CHGJOB RUNPTY(50)

==Kevin Brunk
The Butler Company
Dublin, OH