Re: QCMDEXC question

[John Carr <74711.77@xxxxxxxxxxxxxx>]

RE:     Re: QCMDEXC question

>Try this to see if it works
>
>// DO OPEN FILE, USE USER CONTROL  OPTION>
>
>call 'QCMDEXEC'          XX01XX
>     PARM      CHKOBJ    //CHECK OBJ
>     PARM      PARM2
>
>*IN01     IFEQ *ON
>call 'QCMDEXEC'          XX01XX
>     PARM      CRTBJ          //CRT OBJ
>     PARM      PARM2
>     ELSE
>call 'QCMDEXEC'          XX01XX
>     PARM      OVROBJ    //OVR OBJ
>     PARM      PARM2
>     ENDIF


Ya this looks a lot simpler to understand and maintain than


PGM    (&file)
DCL     &FILE   *CHAR   10

CHKOBJ  &FILE   TYPE(*FILE)
MONMSG  (BLAH BLAH BLAH)  DO
CLRPFM  &FILE
ELSE    DO
CRTPF  &FILE
ENDDO


ENDPGM

OR something like that.  Error handling can be implemented.  Forwarding
of error can be implemented.  Native language(CL) doing what comes 
native(CL commands).

Call bound = little overhead

But the QCMDEXEC  is probably alot easer to read/maintain/debug 
TIC (tongue in cheek)

Is this a SYS/36 APP ??  or in other words Why are you creating files 
on the fly??

Quick trivia test.

Question:   How do you know the app you're working on is a converted 
SYS/36 app????

Ans. It has 3 job steps and it creates 8 temporary work files.

Love those RETAIN-S and RETAIN-J designs
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---