MVSFORUMS.com

radham · Beginner Joined: 04 Nov 2005 Posts: 7 Topics: 4

hi,

I read from the HELP Board about how to allocate REXX execs to the SYSEXEC and SYSPROC. even after doing the same,i am not able to execute the execs by giving the name directly at the command line.i am able To do it,only if give it as TSO before the exec name.

can you please help me in this issue.

1)What settings am i suppose to do so that i can execute the REXX execs by just giving the name of the exec in the command line?

2)Is it required that allocation to SYSPROC ans SYSexec is to be done during every logon to mainframes session?

Thanks in advance.
Radham

ofer71 · Posted: Tue Mar 14, 2006 7:12 am Post subject:

Hi -

If you work with ISPF, then every command that is not an ISPF command must be pre preceded by the TSO keyword. Command that issued without the TSO keywords are condidered as ISPF commands (something like "system commands") for example: SAREA, PFKEY, SETTINGS etc.

You can allocate your REXX/CLIST library to SYSEXEC in your TSO Logon Procedure. To find out your logon-procedure name, use the SAREA command.

O.
________
XL100

German Castillo · Posted: Tue Mar 14, 2006 7:47 am Post subject:

Every Rexx Cmd must be in any Sysexec/Sysproc dataset in order to be executed from the command line. Period. You have to get your datasets in either one of those concatenations, either by modding your startup procedure, dinamically allocating them or Libdefining them.

However, you can allways execute any rexx/clist from the member list directory, by typing in 'EXEC' on the member line cmd, but alas, same basic principles apply here, that is, if you happen to need another exec/panel/skel or so on, those resources MUST be in the proper datasets. To sumarize, executing Rexx like this is a suitable alternative.
_________________
Best wishes,

German Castillo

radham · Beginner Joined: 04 Nov 2005 Posts: 7 Topics: 4

thank u so much

saro · Posted: Sun May 07, 2006 5:02 pm Post subject:

Hi,

can someone explain the exact difference betwen sysexec and sysproc..?
i have noticed sysexec is related to rexx procedures and sysproc to clist.
but what is the difference in functional point of view.

Thanks
_________________
Saro

Nothing is great unless God.

warp5 · Posted: Mon May 08, 2006 12:54 am Post subject:

There are serveral issues here in the original post. What has not been adressed yet is how to allow an Exec to be called without entering TSO before it. Your systems group can make entries in the ISPCMDS for your procedure. Then you do not have to enter TSO in front of the command. There are threads available here on this topic.

semigeezer · Posted: Mon May 08, 2006 8:17 am Post subject:

There is a list of SYSEXEC/SYSPROC differences in the TSO manuals, but the only practical one I know is that if an exec is in SYSEXEC, it does not need the /* REXX ...*/ comment to identify it as Rexx since only Rexx can be in SYSEXEC. But most people add the comment anyway in case someone later installs the exec in the more commonly used SYSPROC, and because it allows the ISPF editor to recognize the file as Rexx for HILITE. Personally, I've never found a use for SYSEXEC, other than as a means of having a specific target for packaging (SMP/E) purposes.