Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Encountering some probs after SYSEXEC change

 
Post new topic   This topic is locked: you cannot edit posts or make replies.    IBMMAINFRAMES.com Support Forums -> TSO/ISPF
View previous topic :: :: View next topic  
Author Message
sushanth bobby

Senior Member


Joined: 29 Jul 2008
Posts: 1013
Location: India

PostPosted: Mon Jan 05, 2009 3:43 pm    Post subject: Encountering some probs after SYSEXEC change
Reply with quote

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
View user's profile Send private message

satheeshkamal

New User


Joined: 09 Jan 2007
Posts: 26
Location: Chennai

PostPosted: Mon Jan 05, 2009 4:31 pm    Post subject:
Reply with quote

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
View user's profile Send private message
sushanth bobby

Senior Member


Joined: 29 Jul 2008
Posts: 1013
Location: India

PostPosted: Mon Jan 05, 2009 4:44 pm    Post subject:
Reply with quote

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
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Mon Jan 05, 2009 5:10 pm    Post subject:
Reply with quote

Take a look at ALTLIB - this is the safest and easiest way to concatenate your own libraries into ISPF.
Back to top
View user's profile Send private message
sushanth bobby

Senior Member


Joined: 29 Jul 2008
Posts: 1013
Location: India

PostPosted: Mon Jan 05, 2009 5:25 pm    Post subject:
Reply with quote

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
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Mon Jan 05, 2009 5:32 pm    Post subject:
Reply with quote

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
View user's profile Send private message
Terry Heinze

JCL Moderator


Joined: 14 Jul 2008
Posts: 1249
Location: Richfield, MN, USA

PostPosted: Mon Jan 05, 2009 9:21 pm    Post subject:
Reply with quote

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
View user's profile Send private message
superk

Moderator Team Head


Joined: 26 Apr 2004
Posts: 4648
Location: Raleigh, NC, USA

PostPosted: Mon Jan 05, 2009 9:28 pm    Post subject: Reply to: Encountering some probs after SYSEXEC change
Reply with quote

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
View user's profile Send private message
Marso

REXX Moderator


Joined: 13 Mar 2006
Posts: 1228
Location: Israel

PostPosted: Mon Jan 05, 2009 10:21 pm    Post subject: Re: Reply to: Encountering some probs after SYSEXEC change
Reply with quote

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
View user's profile Send private message
Pedro

Senior Member


Joined: 01 Sep 2006
Posts: 2038
Location: Silicon Valley

PostPosted: Mon Jan 05, 2009 10:21 pm    Post subject: Reply to: Encountering some probs after SYSEXEC change
Reply with quote

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
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   This topic is locked: you cannot edit posts or make replies.    IBMMAINFRAMES.com Support Forums -> TSO/ISPF All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts How to change 'K' or 'M' use Sort vice_versa DFSORT/ICETOOL 5 Thu May 18, 2017 7:11 am
No new posts Fail to change physical VSAM filename... jacobdng CICS 7 Fri Jan 20, 2017 12:36 pm
No new posts Change date (DD/MM/YY) in 2nd record ... uday kiran DFSORT/ICETOOL 12 Wed Sep 07, 2016 10:57 pm
No new posts How to change dataset attributes of m... ignich7 JCL & VSAM 3 Thu Jul 21, 2016 9:17 pm
No new posts GDG vsersion number change Raghu navaikulam JCL & VSAM 5 Fri May 27, 2016 4:49 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us