RE: QCMDEXEC

If you really want to be true to its 36 roots.....

Run the program in OCL.  When it dies for whatever reason, set on a Ux switch
(i.e. U1-U8) in the RPG program.  This gives you up to 8 error reasons.  In the
OCL, after the program has finished, check the Ux switches and display the
appropriate message.

// if switch1-1 * 'Invald Date'
// if switch1-1 Pause
// if switch1-1 goto end
// if switch2-1 * 'Invalid Customer'
// ......  etc.

This is the way we wrote stuff for the 34/36 TWENTY years ago, but hey, if your
client wants original 36 mode, give them their money's worth.




Kmh0421@aol.com on 03/05/2001 01:17:03

Please respond to RPG400-L@midrange.com

To:   RPG400-L@midrange.com
cc:    (bcc: STEVEN J RYAN/DIAU)

Subject:  RE: QCMDEXEC




Hi to all. I am rewriting some old 36 programs.... getting rid of WSU stuff.
Long story, but due to client demand, must remain in 36 mode. Also per client
demand, constant checks for 'data integrity' are included, always checking
FCR records comparing for all 9's... if not equal, current programs just exit
out of program and write an error record to an error file. I find this
annoying in testing, and I would at least like to add a quick break message
to the user telling them what happenned and why they were blown away. I
checked my books and cannot find a quick little way to do it, and I don't
remember from long ago.... can anyone take a quick minute to refresh my
memory?
Thanks so much;
Kathie