View previous topic :: View next topic
|
Author |
Message |
Pedro
Global Moderator
Joined: 01 Sep 2006 Posts: 2547 Location: Silicon Valley
|
|
|
|
Clearly, it is a CLIST being executed as a rexx program. |
|
Back to top |
|
|
Fathima Begum S
New User
Joined: 02 May 2012 Posts: 3 Location: India
|
|
|
|
Actually, I am learning REXX , and not sure abt many concepts clearly.
Got this piece of code from forum only.
Curious to execute it and got an error in line 5.
/* */
/* INSERTS A JOBCARD AT TOP OF MEMBER */
/* */
ISREDIT MACRO
CONTROL NOCONLIST
ISREDIT RECOVERY OFF
ISREDIT RESET
ISREDIT INSERT: +
ISREDIT LINE_AFTER 0 = "//RAEGVGJ1 JOB (DWARD,SYS),'ACCOUNTS' "
ISREDIT LINE_AFTER 1 = "// CLASS=6, "
ISREDIT LINE_AFTER 2 = "// MSGCLASS=T, "
ISREDIT LINE_AFTER 3 = "// NOTIFY=&SYSUID, "
ISREDIT LINE_AFTER 4 = "// MSGLEVEL=(1,1) "
ISREDIT LINE_AFTER 5 = "//* "
EXIT CODE(0)
@expat: since it is not exactly my code, i have mentioned as to "SOLVE"
Anything wrong in that........ thanks for ur reply. |
|
Back to top |
|
|
Nic Clouston
Global Moderator
Joined: 10 May 2007 Posts: 2455 Location: Hampshire, UK
|
|
|
|
This is an edit macro - you issue the command on the command line whilst editing a dataset - not by TSO commandname. How did you invoke it? |
|
Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011 Posts: 7309 Location: Inside the Matrix
|
|
|
|
If you look at what Pedro wrote...
The code you show does not have a single line of rexx in it.
Everything prefixed by ISREDIT gets shipped out for processing. Leaving:
Code: |
/* */
CONTROL NOCONLIST
EXIT CODE(0)
|
The CONTROL and the EXIT are CLIST commands. Stuff them through the rexx interpreter and certainly the CONTROL will get busted as invalid.... which it did.
It is not rexx, so not such a good example for learning rexx... |
|
Back to top |
|
|
Fathima Begum S
New User
Joined: 02 May 2012 Posts: 3 Location: India
|
|
|
|
Thank you for ur informations.. |
|
Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006 Posts: 2547 Location: Silicon Valley
|
|
|
|
See Appendix C of TSO/E Rexx Users' Guide for a comparison of CLIST vs REXX.
It is not clearly mentioned there, but CLISTs can only be in the SYSPROC concatenation. A REXX program can be in either SYSPROC or SYSEXEC concatenations.
Since either CLISTs and REXX programs can both be in the SYSPROC concatenation, you have to tell the language processor which language it is: rexx programs need to have the first line be a comment with the word 'rexx' in it. |
|
Back to top |
|
|
|