|
View previous topic :: View next topic
|
| Author |
Message |
diwa_thilak
Active User
.jpg)
Joined: 13 Jul 2006
Posts: 205
Location: At my desk
|
|
|
|
Hi All,
i got a rexx program, ( program is to edit/browse a dataset from command prompt).
The program is working fine when executed by giving exec next to the PS in 3.4, but how can i make this particular program be executed from anywhere.
Meaning by giving
tso browse DSN-name (or)
tso %browse DSn-name (where browse is my rexx prg)
The above two commands is not working for me. It is saying browse could not be found.
How can i distribute this code to all my team mates ?
I dont see any CLIST setup here in this new project ? (otherwise i could have concatenated my PDS in the list)
Any suggestions ?
Thanks,
Diwakar
----------------------- |
|
| Back to top |
|
 |
revel
Active User
Joined: 05 Apr 2005
Posts: 135
Location: Bangalore/Chennai-INDIA
|
|
|
|
1. Instead concatinating; execute command like
ALLOC F(SYSPROC) DA(Data set name where REXX exists) SHR REU
2. Try to execute..
Let me know if it not works
Regards,
Raghav |
|
| Back to top |
|
|
diwa_thilak
Active User
Joined: 13 Jul 2006
Posts: 205
Location: At my desk
|
|
|
|
Ragav,
i need to distribute this code to my team.
So do i need to ask my team to execute this command ?
Can anyone tell me , Do we need to give SYSPROC/SYSEXEC in the below command ?
| Quote: |
| ALLOC F(SYSPROC) DA(Data set name where REXX exists) SHR REU |
what difference does it bring ?
Thanks,
Diwakar |
|
| Back to top |
|
|
saiprasadh
Active User
Joined: 20 Sep 2006
Posts: 154
Location: US
|
|
|
|
Hi Diwakar
If you type ISRDDN in the command line , It will display a list of Dataset with the DD Names, In that copy your tool code to the Dataset name against the SYSPROC ddname.
If you did like that , Then your team members can execute your tool by the following command
Thanks
Sai |
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
| I think it's a poor idea to use a name for a REXX exec that's the same as a TSO/ISPF command. I think you should re-consider your naming conventions. |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8796
Location: Welsh Wales
|
|
|
|
| I agree with Kevin |
|
| Back to top |
|
|
diwa_thilak
Active User
Joined: 13 Jul 2006
Posts: 205
Location: At my desk
|
|
|
|
Kevin & Pat,
I totally agree with you. For the sake of explanation i have given the name of my REXX program to be browse.
XBR is the name of the rexx routine.
| Quote: |
| ALLOC F(SYSPROC) DA(Data set name where REXX exists) SHR REU |
Alocating my rexx routine to SYSPROC/SYSEXEC does it make any difference. (Meaning- What is the difference in allocating the rexx to SYSPROC & SYSEXEC)
If you got any link you can share the link with me.
Thanks,
Diwakar |
|
| Back to top |
|
|
ofer71
Global Moderator
Joined: 27 Dec 2005
Posts: 2358
Location: Israel
|
|
|
|
You can find the answer to your question in the fine manual.
O. |
|
| Back to top |
|
|
diwa_thilak
Active User
Joined: 13 Jul 2006
Posts: 205
Location: At my desk
|
|
|
|
Hi friends,
I need a small clarification.
If we update the PDS name in the SYSEXEC/SYSPROC it stays only for that particular session - am i rt ?
If so how can we update the name forever in that ?
There can be suggestion like execute a CLIST by adding the dataset , but i dont find any CLIST component in my project(ie. #setup file).
Is the SYSEXEC/SYSPROC is Mainframe id dependent (that means if i update PDS name will it visible to all my team mates) ? i suppose yes, if so how can we make a common tool accessible to everybody ?
Without CLIST, (#setup file) how can identify the script which is executing in the startup ?
Ofer, Kevin, Pat - Thanks buddies, i really learnt a lot from you ppl.
Thanks,
Diwakar
-----------------------------------------------------
Nobody is Perfect. I am Nobody |
|
| Back to top |
|
|
Aaru
Senior Member
Joined: 03 Jul 2007
Posts: 1287
Location: Chennai, India
|
|
|
|
A similar topic was discussed yesterday in this forum. Please
find below the link
[url]http://ibmmainframes.com/viewtopic.php?t=24259 [/url]
| Quote: |
| How can i distribute this code to all my team mates ? |
You will have to put this exec in a common PDS ( which can be accessed by all) allocated to either SYSEXEC or SYSPROC.
| Quote: |
Alocating my rexx routine to SYSPROC/SYSEXEC does it make any difference.
(Meaning- What is the difference in allocating the rexx to SYSPROC & SYSEXEC) |
Yes, To execute your rexx exec using TSO <member name> you will have to allocate that.
| Quote: |
| If we update the PDS name in the SYSEXEC/SYSPROC it stays only for that particular session - am i rt ? |
No, It stays until you deallocate it. But i have not tried deallocating any PDS.
| Quote: |
Is the SYSEXEC/SYSPROC is Mainframe id dependent
(that means if i update PDS name will it visible to all my team mates) ?
i suppose yes, if so how can we make a common tool accessible to everybody ? |
Yes, You are rite. It can accessed by everybody if you allocate a common PDS to SYSEXEC/SYSPROC. If you
allocate a PDS starting with your qualifier, then only you can run this exec using TSO command.
Hope this helps, else post your queries |
|
| Back to top |
|
|
agkshirsagar
Active Member
Joined: 27 Feb 2007
Posts: 691
Location: Earth
|
|
|
|
| Quote: |
| If we update the PDS name in the SYSEXEC/SYSPROC it stays only for that particular session - am i rt ? |
Aaru,
By this OP meant, after you log off and again log in, the changes you did will be lost.
Diwakar,
I will suggest you to talk to some senior guy in the project, so that he will be able to tell him about 'editing logon exec'.
If you successfully add your PDS in SYSPROC in your logon procedure then your work is done! But be careful while doing so. I will suggest doing ALTLIB for testing your codes. |
|
| Back to top |
|
|
diwa_thilak
Active User
Joined: 13 Jul 2006
Posts: 205
Location: At my desk
|
|
|
|
Hi All,
Aaru,
thanks for your reply.
| Quote: |
If we update the PDS name in the SYSEXEC/SYSPROC it stays only for that particular session - am i rt ? |
But according to me/project, the allocated PDS in SYSEXEC/SYSPROC stays only for the particular session. That is the reason we have CLIST member (#setup) which will allocate the datasets at login time.
Abhijit,
Thanks buddy, i will check and post, if i found anything interesting.
Any views for this below quote.
| Quote: |
Is the SYSEXEC/SYSPROC is Mainframe id dependent
(that means if i update PDS name will it visible to all my team mates) ?
i suppose yes, if so how can we make a common tool accessible to everybody ? |
I still beleive that is the reason we have the CLIST member, which will allocate the datasets of other members into our SYSEXEC and SYSPROC ?
Anyother views ?
Thanks,
Diwakar
------------------
Nobody is Perfect. I am Nobody |
|
| Back to top |
|
|
agkshirsagar
Active Member
Joined: 27 Feb 2007
Posts: 691
Location: Earth
|
|
|
|
Diwakar,
Yes, SYSPROC/SYSEXEC are mainframe ID dependent, that is it can be different for different user. When you allocate PDS to SYSPROC, it will be effective to your id only.
| Quote: |
| that means if i update PDS name will it visible to all my team mates? |
What do you want to say by the term visibility here?
If you create PDS with userid prefix 'userid.pds' then it will not be available to other users, look for HLQ which is accessible to your group of users. If you create PDS using HLQ.PDSNAME then it will be visible to all your teammates. For them to use the tools you have created, they also need to allocate that PDS to their SYEXEC/SYSPROC |
|
| Back to top |
|
|
diwa_thilak
Active User
Joined: 13 Jul 2006
Posts: 205
Location: At my desk
|
|
|
|
| Thanks Abhijit |
|
| Back to top |
|
|
agkshirsagar
Active Member
Joined: 27 Feb 2007
Posts: 691
Location: Earth
|
|
|
|
Good to see that it helped you!  |
|
| Back to top |
|
|
Aaru
Senior Member
Joined: 03 Jul 2007
Posts: 1287
Location: Chennai, India
|
|
|
|
| Quote: |
But according to me/project, the allocated PDS in SYSEXEC/SYSPROC stays only for the particular session.
That is the reason we have CLIST member (#setup) which will allocate the datasets at login time. |
Even we have a similar CLIST member($SETUP) in our site which allocates the datasets at login time using TSOALLOC command. But even then all the allocated datasets and PDS stays till we deallocate and not just till we logoff.  |
|
| Back to top |
|
|
agkshirsagar
Active Member
Joined: 27 Feb 2007
Posts: 691
Location: Earth
|
|
|
|
Aaru,
Where is the confusion in this? When you 'deallocate' dataset, system will do whatever you asked for. Allocating PDS in LOGON procedure does not mean it will be allocated forever or for that matter 'till you logoff' |
|
| Back to top |
|
|
Aaru
Senior Member
Joined: 03 Jul 2007
Posts: 1287
Location: Chennai, India
|
|
|
|
| Oh ok ! Its clear now. Thanks. |
|
| Back to top |
|
|
revel
Active User
Joined: 05 Apr 2005
Posts: 135
Location: Bangalore/Chennai-INDIA
|
|
|
|
Hi all,
Just i want to add some wards for SYSPROC and SYSEXEC
1) When tool developed using CLIST(say in X.Y.Z data set), Allocate X.Y.Z dataset to SYSPROC
2) When tool developed using REXX(say in A.B.C data set), allocate A.B.C data set to SYSEXEC
When we allocate dataset, we can execute Tools globally only for that session(that is also called implicit execution)
If we need execute Tools globally(mean for every session), we should append A.B.C data set to ALLOCATE Command which is present in LOGON PROC(these are system sided---this is the PROC used while u logon to TSO SESSION)
See code below for sample LOGON PROC
We can execute REXX
//soft.. JOB ....
//SOFTUSR EXEC SOFTUSR ----------> where SOFTUSR is LOGON PROC
------------------------------------------------------------------------------------
-- See expanded LOGON PROC --
------------------------------------------------------------------------------------
xxSOFTUSR PROC
xxSOFTUSR EXEC PGM=IKJEFT01, DYNAMBR=175...
XXSYSUADS DD DSN=SYS1.UADS,DISP=SHR
XXSYSPROC DD DSN=HLQ.Z0SV14S.CLIST,DISP=SHR
------------------------------------------------------------------------------------
-- HLQ.Z0SV14S.CLIST CONTAINS SET OF STATMENT
--
-- ALLOC F(SYSPROC) DA('USER.CLIST' +
-- 'ADCD.ZS014V14.CLIST' +
-- .
.
U CAN APPEND YOUR DATA SET HERE; TO EXECUTE TOOLS GLOBALLY
----------------------------------------------------------------------------------
--
.
.
.
.
Any suggestion is welcomed
Thanks & Regards,
Raghavendra K N |
|
| Back to top |
|
|
ofer71
Global Moderator
Joined: 27 Dec 2005
Posts: 2358
Location: Israel
|
|
|
|
revel -
You said
| Quote: |
1) When tool developed using CLIST(say in X.Y.Z data set), Allocate X.Y.Z dataset to SYSPROC
2) When tool developed using REXX(say in A.B.C data set), allocate A.B.C data set to SYSEXEC |
This is not true. Please read the fine manual before posting misleading information.
O. |
|
| Back to top |
|
|
revel
Active User
Joined: 05 Apr 2005
Posts: 135
Location: Bangalore/Chennai-INDIA
|
|
|
|
Sorry for misleading,
What i meant was,
-----------------------------------------------------------------------------------
Structure and General Syntax
_________________________
If you store a REXX exec in a data set that is allocated to SYSPROC, the exec must start with a comment and the comment must contain the characters “REXX” within the first line (line 1) of the exec. This is known as the REXX exec identifier and is required in order for the TSO/E EXEC command to distinguish REXX execs from TSO/E CLISTs, which are also stored in SYSPROC.
Refered from TSO/E REXX Referance from IBM
------------------------------------------------------------------------------------
Thanks & Regards,
Raghav |
|
| Back to top |
|
|
|
|
