|
View previous topic :: View next topic
|
| Author |
Message |
Renato Zangerolami
New User
Joined: 06 Dec 2019
Posts: 28
Location: Brazil
|
|
|
|
Can anyone tell me if:
Sysexec runs only on my profile and is lost every time I log off?
Can Sysproc be shared with other profiles?
Or do sysexec and sysproc have the same function, what differentiates them between the profile and the volume setting? |
|
| Back to top |
|
 |
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
From the manual at www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ikjb300/ikjb30044.htm :
| Quote: |
TSO/E provides a system file, SYSEXEC, that can contain REXX execs only. You can use the SYSEXEC file to store execs in both TSO/E and non-TSO/E address spaces.
In TSO/E, the SYSPROC system file can contain REXX execs as well as TSO/E CLISTs. If you store a REXX exec in a PDS that is allocated to SYSPROC, the exec must begin with a comment and the first line of the comment must include the characters "REXX". This is required in order for the TSO/E EXEC command processor, during implicit execution, to distinguish REXX execs from CLISTs, which are also stored in data sets that are allocated to SYSPROC.
If you store your REXX execs in a PDS that is not allocated to SYSPROC, you do not need to begin the execs with a comment. However, it is recommended that you start all execs with a comment in the first column of the first line and include the characters REXX in the comment. In particular, this is recommended if you are writing REXX execs for use in other SAA environments. It is also recommended that you include the characters REXX in the first line of the comment to help users identify the program as a REXX exec.
If your installation will primarily use REXX, it is recommended that you use SYSEXEC for your REXX execs. Using SYSEXEC makes it easier to maintain your REXX execs and is also useful for execs that you use on other SAA environments. If your installation primarily uses CLISTs and does not plan to have a large number of REXX execs, you can use SYSPROC for your CLISTs and REXX execs. |
So they do NOT have the same function as you asked.
What does your logon procedure look like? Our contains //SYSPROC as well as //SYSEXEC so they are both permanently allocated and will not be lost upon log off. Some of what you are asking is entirely dependent upon how your local site does things -- and that is something you CANNOT find out here; you MUST talk to your site support group to find out how things are done AT YOUR SITE. |
|
| Back to top |
|
|
Renato Zangerolami
New User
Joined: 06 Dec 2019
Posts: 28
Location: Brazil
|
|
|
|
In my logon it has only SYSPROC.
When I use the alloc file (sysproc), I overwrite the sysproc of the system, that is, I check the ISRDDN and realize that the only active sysproc is the one I allocated. When I log off and log on, the system sysproc returns to be displayed on ISRDDN.
2 doubts:
- when i allocate a dataset in the sysproc do i overwrite the sysproc of the system? Or is that just an illusion? Because when I allocate the sysproc, only my allocated sysproc is visible.
-Is there a command that I can use to allocate a dataset permanently in sysexec / sysproc, or is that defined in the group settings, racf ..? |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| Quote: |
| - when i allocate a dataset in the sysproc do i overwrite the sysproc of the system? Or is that just an illusion? Because when I allocate the sysproc, only my allocated sysproc is visible. |
A DD name is unique to a step or TSO session -- if you allocate to SYSPROC then the system SYSPROC will not be kept. You could use ALTLIB to change this behavior.
| Quote: |
| -Is there a command that I can use to allocate a dataset permanently in sysexec / sysproc, or is that defined in the group settings, racf ..? |
Talk to your site support group -- //SYSPROC or //SYSEXEC in your logon procedure will stay around (unless, of course, you change the allocation in your session). |
|
| Back to top |
|
|
Renato Zangerolami
New User
Joined: 06 Dec 2019
Posts: 28
Location: Brazil
|
|
|
|
| Thank you for clarifying my doubts Robert. |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
It is probably the terminology that makes it confusing.
1. If you use the ALLOC command for a data set name and also specify the NEW parameter, then a permanent data set is created. It will last until somebody deletes it.
2. If you use the ALLOC command for a FILE or DDNAME, it is a setup for the use of a data set. This setup is only good for the current job step or TSO session, or until the next ALLOC command of same FILE, or until FREE command is issued.
You can use ALLOC FILE(myfile) DATASET(mydsn) in the same command instance. myfile will go away when you log off, but mydsn can last beyond. |
|
| Back to top |
|
|
Renato Zangerolami
New User
Joined: 06 Dec 2019
Posts: 28
Location: Brazil
|
|
|
|
Hello Pedro, that's exactly what I did, I used the command ALLOC FILE (myfile) DATASET (mydsn).
I am aware that the dataset will have been created for a long time.
Thank you. |
|
| Back to top |
|
|
|
|
