RE: Oh No... How do I run commands in S36 environment?

["Dan Riehl" <dan.riehl@xxxxxxxxxxxxx>]

Yes.... that was the point of the CHKOBJ... to see if it was a CL
command.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Monday, August 04, 2008 9:16 AM
To: Midrange Systems Technical Discussion
Subject: Re: Oh No... How do I run commands in S36 environment?

I was thinking he'd do:

      CHKOBJ OBJ(*LIBL/&CMDNAME) OBJTYPE(*CMD)

And if it failed (i.e. didn't find a command with that name) he'd simply

ASSUME it was an S/36 proc.



Jerry Adams wrote:
> Couple of things.  First, CHKOBJ may be problematic against 36
> "commands."  As you probably know, these are really source members,
> not objects, that reside in the QS36PRC source physical file.  I just
> ran a test of CHKOBJ using *LIBL and, if the procedure/command (which
> does exist in the library) is not in the first source PF, CHKOBJ
> returns a 'not found' error.  So you will have to know the specific
> library or, as in my test, use *CURLIB if the procedure is supposed
> to be there.
>
> Second, are these really always going to be *CMD objects or might
> they be CL *PGM objects from time-to-time?