|
View previous topic :: View next topic
|
| Author |
Message |
sushanth bobby
Senior Member
Joined: 29 Jul 2008
Posts: 1020
Location: India
|
|
|
|
I modified the following allocation according to my shop
| Code: |
/******REX******/
"EXECUTIL SEARCHDD(YES)" /* TO ENSURE THAT SYSEXEC IS AVAILABLE*/
"ALLOC FILE(SYSEXEC) DATASET(REXX.EXEC,",
"'SYS1.PROD.OEM.ISPRLIB') SHR REUSE"
IF RC = 0 THEN
SAY 'ALLOCATION TO SYSEXEC COMPLETED.'
ELSE
SAY 'ALLOCATION TO SYSEXEC FAILED.' |
It executed successfully. I got message "ALLOCATION TO SYSEXEC COMPLETED".
Now the thing is, now i am not able to use usual commands to view a dataset.
LIke, 34 --> i enter some naming convention --> find the dataset & type 'V' before it to view it. I get error there like
| Code: |
v HXSULL.QUERYRES
.
.
.
COMMAND VWEX NOT FOUND
*** |
And one more thing....
Before executing the REXX, i used TSO ISRDDN command to see what are the dataset that were in SYSEXEC
| Code: |
SYS1.PROD.OEM.ISPRLIB
SYS3.QPP1N.INFOX.EXEC
SYS1.PROD.NLIC.ISPRLIB
ISP.SISPEXEC
SYS1.SBPXEXEC
NLV1.EXECLIB |
After executing the above REXX, i have only 2
| Code: |
HXSULL.REXX.EXEC
SYS1.PROD.OEM.ISPRLIB |
When i logout and login, the problem is gone. |
|
| Back to top |
|
 |
satheeshkamal
New User
Joined: 09 Jan 2007
Posts: 28
Location: Chennai
|
|
|
|
The code which you have shown overrides all the SYSEXEC libraries, becuase of that, you can not use the usual commands in your shop.
Try this...
The following code concatenates your rexx library to all the other SYSEXEC...
| Code: |
DSNAME = "'REXX.EXEC'" || "," || "'SYS1.PROD.OEM.ISPRLIB'"
DDNAME = 'SYSPROC'
ADDRESS ISPEXEC "QBASELIB" DDNAME "ID(DSLIST)"
"ALLOC F("DDNAME") DA("DSNAME","DSLIST") SHR REUSE" |
|
|
| Back to top |
|
|
sushanth bobby
Senior Member
Joined: 29 Jul 2008
Posts: 1020
Location: India
|
|
|
|
Satheesh,
Firstly i got an error in "rexx.exec". So, i added my HLQ HXSULL in the code you gave
| Code: |
DSNAME = "'HXSULL.REXX.EXEC'" || "," || "'SYS1.PROD.OEM.ISPRLIB'"
DDNAME = 'SYSPROC'
ADDRESS ISPEXEC "QBASELIB" DDNAME "ID(DSLIST)"
"ALLOC F("DDNAME") DA("DSNAME","DSLIST") SHR REUSE" |
Now, i am getting following error message.
| Code: |
DATA SET HXSULL.DSLIST NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED
DATA SETS NOT CONCATENATED+
FAILURE TO ALLOCATE DATA SET HXSULL.DSLIST |
And sorry guyz, It was REXX setup, so i post it up in REXX.
Sushanth |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
| Take a look at ALTLIB - this is the safest and easiest way to concatenate your own libraries into ISPF. |
|
| Back to top |
|
|
sushanth bobby
Senior Member
Joined: 29 Jul 2008
Posts: 1020
Location: India
|
|
|
|
Expat,
| Code: |
| ADDRESS ISPEXEC "QBASELIB" DDNAME "ID(DSLIST)" |
Is this code shop Specific....
And i came across this code from this link
| Code: |
/* REXX SETUP */
"ALTLIB DEACTIVATE APPL(EXEC)"
"ALTLIB ACTIVATE APPL(EXEC) DSN('SRINI.REXX.EXEC')" |
Is this also another method of setup or something else.
Sushanth |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
I've never seen the first code before, so it may be shop specific.
ALTLIB is just an easy way to change your SYSEXEC / SYSPROC concatenations on the fly. I've used it countless times with never a problem, and of course you have no need to deallocate and reallocate the default ISPF libraries.
Soooooooooooooooooooo much easier and safer than dealloc / realloc |
|
| Back to top |
|
|
Terry Heinze
JCL Moderator
Joined: 14 Jul 2008
Posts: 1249
Location: Richfield, MN, USA
|
|
|
|
| I'm also a fan of using ALTLIB. The only downside I've encountered is that in split screen mode, the ALTLIB is effective only in the screen you've defined it in. |
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
I've never used that QBASELIB command before, but now that I've seen what it does it's definitely one to add to my bag of tricks. I tried the original code and it worked just fine for me. All it did was add the library I specified to the top of the concatenation list for SYSPROC. I don't see why something like this couldn't be added to a user's TSO logon procedure as the last step.
Of course, I keep having to ask the question: why should a user need to add their own libraries to the logon concatenation? Shouldn't their sysprog's define a common set of both development and production TSO and ISPF libraries that everyone can share and use? |
|
| Back to top |
|
|
Marso
REXX Moderator
Joined: 13 Mar 2006
Posts: 1353
Location: Israel
|
|
|
|
| superk wrote: |
| Of course, I keep having to ask the question: why should a user need to add their own libraries to the logon concatenation? Shouldn't their sysprog's define a common set of both development and production TSO and ISPF libraries that everyone can share and use? |
As a rexx programmer, I want to run the prod version of some rexx, or to run my modified version. So sometimes I have to change my SYSEXEC concatenation.
Anyway, I've looked around and found something interesting: in the TSO/E Command Reference, Paragraph 1.8.1, Search Order for Libraries
there is mention of SYSUEXEC and SYSUPROC.
They are at the top of the search order, and they may exist just for this purpose (to add your own library...). |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
I prefer having my personal libraries so I can try things easily. Sometimes I tweak the existing programs for my personal use and without affecting everyone else.
This approach is not good for everyone. |
|
| Back to top |
|
|
|
|
