MVSFORUMS.com Forum Index MVSFORUMS.com
A Community of and for MVS Professionals
 
 FAQFAQ   SearchSearch   Quick Manuals   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Problem with rexx tool

 
Post new topic   Reply to topic   printer-friendly view    MVSFORUMS.com Forum Index -> TSO and ISPF
View previous topic :: View next topic  
Author Message
vjkumk
Beginner


Joined: 28 Sep 2005
Posts: 98
Topics: 33

PostPosted: Wed Jan 11, 2006 9:41 am    Post subject: Problem with rexx tool Reply with quote

i have created a Rexx tool and i allocated to SYSPROC,the problem is, after i allocate the rexx tool (pds where it resides) to SYSPROC some of already available REXX tools in our shop is not working.(i also freed the sysproc)it says like command not found.If i logoff from the system and logon again ,the already available Rexx tool is working fine.So what is the problem?
Back to top
View user's profile Send private message
moyeenkhan
Beginner


Joined: 04 Dec 2002
Posts: 64
Topics: 21

PostPosted: Wed Jan 11, 2006 11:44 am    Post subject: Reply with quote

Issue TSO LIST ST.
LOcate SYSPROC datasets.
Add your PDS to this set.
Check up with your shop. Differant shops have differant standards for including SYSPROCs.

ALternatively you can issue TSO ALTLIB and follow the prompts
Back to top
View user's profile Send private message Send e-mail
ofer71
Intermediate


Joined: 12 Feb 2003
Posts: 358
Topics: 4
Location: Israel

PostPosted: Wed Jan 11, 2006 2:44 pm    Post subject: Reply with quote

LIST is not a TSO command.

O.
________
home made vaporizer


Last edited by ofer71 on Sat Feb 05, 2011 11:26 am; edited 1 time in total
Back to top
View user's profile Send private message Send e-mail
superk
Advanced


Joined: 19 Dec 2002
Posts: 684
Topics: 5

PostPosted: Wed Jan 11, 2006 3:46 pm    Post subject: Reply with quote

It's TSO LISTALC STATUS.
Back to top
View user's profile Send private message
vjkumk
Beginner


Joined: 28 Sep 2005
Posts: 98
Topics: 33

PostPosted: Thu Jan 12, 2006 9:48 am    Post subject: Reply with quote

superk,moyeenkhan,ofer71

i checked with what you guys said.It shows the list of dataset allocated for system DDNAME.I also checked with the TSO ISRDDN..

by default the SYSPROC ddname is allocated to the dataset which contains the tool library used in our shop.If i used a rexx program to allocated my rexx pds to sysproc and checked the Sysproc ddname using the TSO ISRDDN,the SYSPROC is allocated to my rexx tool PDS.(I am not sure that the sysproc is concated with many pds like my rexx tool pds at top and my default tool library as next).If the syproc is concated with many pds.then my default rexx tool should work right?

my rexx pgm which allocates my rexx tool pds to sysproc.

"alloc fi(sysproc) da('"pds containg my rexx tools"') shr reuse"
exit
Back to top
View user's profile Send private message
semigeezer
Supermod


Joined: 03 Jan 2003
Posts: 1014
Topics: 13
Location: Atlantis

PostPosted: Thu Jan 12, 2006 10:43 am    Post subject: Reply with quote

"alloc fi(sysproc) da('"pds containg my rexx tools"') shr reuse" does not concatenate the old libraries. It frees them. Check ISRDDN after you do the allocation and you will see that the original libraries are gone.

In ISRDDN type SAVE SYSPROC, modify that file ('userid.ISRDDN.CLIST') and run it. The modification is to add your pds name before the others.
Back to top
View user's profile Send private message Visit poster's website
ha.rajamohamed
Beginner


Joined: 29 Jan 2006
Posts: 71
Topics: 22

PostPosted: Sun Jan 29, 2006 11:31 pm    Post subject: Reply with quote

Even doing the above, I am unable to Run the REXX program from my dataset, its saying the following error.
Is there any specification we need to have for the dataset we are having the REXX programs ?
PHASE 1 PROCESSING OF CLIST OR REXX EXEC ENDED ABNORMALLY +
ABEND CODE: S66D REASON CODE: 004D
***
_________________
RAJA MOHAMED
Back to top
View user's profile Send private message
semigeezer
Supermod


Joined: 03 Jan 2003
Posts: 1014
Topics: 13
Location: Atlantis

PostPosted: Mon Jan 30, 2006 1:11 am    Post subject: Reply with quote

I forget what causes this exact message, but be sure your PDS has the same record format and record length as the data sets you are concatenating it to. In ISRDDN, press RIGHT (usually PF11) and look at the Lrecl and RCFM columns. Also be sure that your Rexx exec starts with a comment with the word 'rexx' in it such as /* Rexx */

It appears that the CLIST interpreter has control, not the Rexx interpreter so it is probably the comment thing.

update: the fine manual indicates that it is the concatenation problem, not the comment problem.
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic   printer-friendly view    MVSFORUMS.com Forum Index -> TSO and ISPF All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


MVSFORUMS
Powered by phpBB © 2001, 2005 phpBB Group