|
View previous topic :: View next topic
|
| Author |
Message |
twissi
Active User
Joined: 01 Aug 2005
Posts: 105
Location: Somerset, NJ
|
|
|
|
All,
I overrode SYSPROC libraries while trying to add a dataset to SYSPROC; I'm unable to log on to that region on mainframe.
Could anyone please tell me how to get this resolved without involving the IBM OPS?
Many thanks, Twissi |
|
| Back to top |
|
 |
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| You'll need to explain much more before you can get coherent help: overrode SYSPROC lbiraries where? how did you do the override? what error message(s) show up when you try to log on? |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
Twissi,
did you modify your signon PROC? |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
any advice given without a deep knowledge of You environment,
will more than often be wrong and lead to more damage
You fouled up things, do nothing, put away Your pride and ask Your support to fix it
a technically correct, but useless advice, would be to
try to remember exactly what You did and and .... rebuild what is not there any longer
I always advised against using the full 8 chars allowed for logon procedures
in order to have at least one char to trace the last 10 for example modifications
and be able to fall back |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
| Quote: |
| I overrode SYSPROC libraries |
Undo your changes. |
|
| Back to top |
|
|
twissi
Active User
Joined: 01 Aug 2005
Posts: 105
Location: Somerset, NJ
|
|
|
|
Lot of questions and comments...! I'll try to answer/explain them:
Robert - I executed a REXX with the following command as I wanted to assign a PDS to SYSPROC:
| Code: |
| "ALLOC FI(SYSPROC) DA('RACF.MY.PDS') SHR REUSE" |
It then de-assigned everything from SYSPROC and allocated only my PDS.
I was then thrown out of that region and when I tried to log on, I was getting the message given below:
| Code: |
IKJ56500I COMMAND $SETSYS NOT FOUND
*** |
My sign-on data was deleted...!
I solved the problem by running the following command where the error message was appearing:
| Code: |
| ALTLIB ACTIVATE SYSTEM(*) |
This may be shop specific , no support guys were called for!
Cheers, Twissi |
|
| Back to top |
|
|
Bill Dennis
Active Member
Joined: 17 Aug 2007
Posts: 562
Location: Iowa, USA
|
|
|
|
| You could also LOGOFF completely from TSO and LOGON again. This will get you a fresh allocation of libraries from the logon PROC and negate your ALLOC actions. |
|
| Back to top |
|
|
twissi
Active User
Joined: 01 Aug 2005
Posts: 105
Location: Somerset, NJ
|
|
|
|
| Bill Dennis wrote: |
| You could also LOGOFF completely from TSO and LOGON again. This will get you a fresh allocation of libraries from the logon PROC and negate your ALLOC actions. |
I tried that too but didn't work. I waited even 1 day just to see if some batch jobs did the job for me but nothing happened as well. |
|
| Back to top |
|
|
|
|
