|
View previous topic :: View next topic
|
| Author |
Message |
Akatsukami
Global Moderator
Joined: 03 Oct 2009
Posts: 1788
Location: Bloomington, IL
|
|
|
|
OK, that indicates that RXSUBCOM is not in an allocated load library.
I'm a bit uncertain how to proceed here. It would be easy enough to invoke RXSUBCOM, but as you've been told, RXSUBCOM is an alias for DSNREXX, the IBM Rexx/DB2 interface, and there's no way to specify to TSO that it should use a command processor not in STEPLIB/LPA/linklist. I can see a couple of possibilities, but I'll need to do some experimentation when I get into my office, which won't be for a couple of hours yet. |
|
| Back to top |
|
 |
devmisra
New User
Joined: 29 Jan 2009
Posts: 39
Location: India
|
|
|
|
Thank you Akatsukami..
I also was trying TSOLIB ACTIVATE but its also throwing an error
| Code: |
IDY00046I TSOLIB terminated. A valid TSOLIB environment does not exist.+
IDY00046I The TSOLIB command with the ACTIVATE, DEACTIVATE or RESET operands mu
st be invoked from the TSO/E READY environment.
|
|
|
| Back to top |
|
|
don.leahy
Active Member
Joined: 06 Jul 2010
Posts: 765
Location: Whitby, ON, Canada
|
|
|
|
The TSO READY environment (aka the "READY prompt") is what you see when you exit ISPF in order to issue the LOGOFF command. That is where the TSOLIB command needs to be issued.
I mentioned earlier that I pick up RXSUBCOM from ISPLLIB. What I failed to mention is that my ISPLLIB allocation is set up by my logon proc before the ISPF environment is initiated. LIBDEF can be used to add libraries to ISPLLIB, but not every software product can see them.
If you have access to your logon procedure, then ISPLLIB would probably be the easier way to go. If not, then try TSOLIB from the READY prompt. |
|
| Back to top |
|
|
devmisra
New User
Joined: 29 Jan 2009
Posts: 39
Location: India
|
|
|
|
Thanks Don.leahy,
Yes.. i just TSOLIBd the SDSNLOAD and now i am able to connect to DB2
| Code: |
23 *-* s_rc= RXSUBCOM('ADD','DSNREXX','DSNREXX')
24 *-* say s_rc
0
25 *-* /**/
26 *-* ADDRESS DSNREXX "CONNECT "ssid
>>> "CONNECT VFST"
27 *-* say RC
0
29 *-* exit
|
Well, one question,
Is not any other way to allocate the SDSNLOAD? |
|
| Back to top |
|
|
Nic Clouston
Global Moderator
Joined: 10 May 2007
Posts: 2455
Location: Hampshire, UK
|
|
|
|
| Quote: |
| Is not any other way to allocate the SDSNLOAD? |
Ask your incompetent support people to sort it out for you. |
|
| Back to top |
|
|
devmisra
New User
Joined: 29 Jan 2009
Posts: 39
Location: India
|
|
|
|
Thank you so much.. Thanks a lot...
Thank you Akatsukami, Don.leahy,Enrico & Yuvraj and all the experts.
Morning starts with a very good result..
TSOLIBd the LOAD DSN & allocated to ISPLLIB in LOGON procedure. Now am able to connect to DB2 and its working.
I may come to you again if I face any issues.
A request to Moderators,
Please change the word from VFST to XXXT or something else.
Thanks a lot. |
|
| Back to top |
|
|
|
|
