|
View previous topic :: View next topic
|
| Author |
Message |
Ekta Sharma
New User
Joined: 26 Feb 2008
Posts: 35
Location: pune
|
|
|
|
I have created an ISPF panel (named PANEL1) and a rexx code (named REX1) to invoke the panel. Both these rexx and panel code are residing in my pds named "Y00055.TEMP.UTILITY".
The rexx code consists of following line of code:
"ISPEXEC LIBDEF ISPPLIB DATASET ID('Y00055.TEMP.UTILITY)"
I wanted to use it from ISPF Primary Menu, so I copied the rexx code (REX1) to my CLIST. Now if I do TSO REX1 on the primary menu, it takes me to the panel.
Queries:
1. What I want is that others should also be able to use my panel. Is there a way thru which I can remove my PDS name 'Y00055.TEMP.UTILITY from the rex code ("ISPEXEC LIBDEF ISPPLIB DATASET ID('Y00055.TEMP.UTILITY)")?
2. The above LIBDEF statement has not added my panel to ISPPLIB (I have checked it using TSO ISRDDN). I even tried adding it thru 7.6 option. Still it's not added to ISPPLIB. If I try to copy my PDS member (holding the panel code) directly to ISPPLIB lib then it gives authorization faild. How can I do this? |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
talk to Your support group on the standards to be used when building tools to be shared among many users
libraries
naming convention( to void tool clashing )
documentation standards
maintenance agreement
.... add as many standards and pratices issues as You want |
|
| Back to top |
|
|
Ekta Sharma
New User
Joined: 26 Feb 2008
Posts: 35
Location: pune
|
|
|
|
If I copy my rexx code(REX1) in someone else's CLIST then it works fine for them when first time TSO REX1 is given on the primary menu. But second time on giving TSO REX1 on primary menu it abends saying:
"FAILED BECAUSE DIRECTORY ENTRY IS NOT VALID FOR A LOAD MODULE.
abended with code 806000. Load module not found."
What could be a possible cause? Is it b'coz of my PDS name been used in the rexx code? |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
are You sure You copied things to the right dataset
looks like You just messed up a load library
why don' t just follow the advice I gave You in the previous post |
|
| Back to top |
|
|
Ekta Sharma
New User
Joined: 26 Feb 2008
Posts: 35
Location: pune
|
|
|
|
Talking to the support group is not possible at the moment. So I am trying if I can find out some alternative solution.
What happens is:
On my TSO, when I use TSO REX1 on primary menu for the first time, it creates an entry for my PDS with a new ddname in ISRDDN.
But when I try the same thing on someone else's TSO, using TSO REX1 for the first time opens my panel but it does not create any entry in their ISDDN (might be b'coz it's my PDS, not accessible to others). So for the second time it is not able to find the load module and hence it abends. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
since little is know about Your organization standards and setup
any advice will certainly be the wrong one
if sharing the application is urgent/mission_critical, support should be available to advice on how to proceed
any other choice is just Yours, but I warned You  |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
| Quote: |
| The above LIBDEF statement has not added my panel to ISPPLIB |
You are right, LIBDEF does not alter the ISPPLIB concatenation, but instead adds another DD name that ISPF searches first.
You need a setup exec that:
1. adds your rexx library to the SYSEXEC concatenation
2. adds your panel library to the ISPPLIB concatenation.
Run the setup exec before starting ISPF.
Get each of your colleagues / team members to call your setup exec as the 'initial command' when they logon, so that it is performed automatically.
What is 'Y00055'? If it is your userid, I suggest that you create the datasets under a different high level qualifier. Perhaps a HLQ of 'tools' or something like that. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| Quote: |
| .... Perhaps a HLQ of 'tools' or something like that. ..... |
I am still of the idea that asking support is be the wisest thing to do  |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
| Quote: |
| asking support is the wisest thing |
Always!
I think the application stack (order of concatenation) should be in this order:
| Code: |
user written
group
location
vendor
ISPF
|
I think system support will provide the last three or four levels, but might not care much about the first few.
That is, I think Ekta falls in the 'wow, so proud of myself that I feel compelled to share with person in next cubicle' category rather than as support for local apps. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
One caution with having the "user written" library(ies) first is that someone may unwittingly use a name that already belongs to some other library. Surprise is somthing of an understatement  |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
Yes, that is safer.
On the otherhand, there are other times when you want to override one of the system panels... such as ISR@PRIM with their own options.
I used to be in system support... part of the normal problem determination was to remove the users' personal customization. |
|
| Back to top |
|
|
|
|
