Contention for PDS after executing Rexx



IBM's Command List programming language & Restructured Extended Executor

Re: Contention for PDS after executing Rexx

Postby mvmanish » Sat Feb 04, 2017 2:01 am

Robert Sample wrote:
instead of closing the LPAR do I need to put that in contention :x or do you have any better idea..
Log off TSO and log back on.
If you have console access, cancel your TSO user id.

Doing an IPL of the LPAR should be the LAST resort if nothing else works -- NOT a normal operation.


Even If I logoff and logon, LPAR will be in open. I have to cancel them. Cancelling my id may work. Anyhow I got solution for my problem :D
mvmanish
 
Posts: 10
Joined: Fri Mar 11, 2016 1:25 am
Has thanked: 1 time
Been thanked: 0 time

Re: Re: Contention for PDS after executing Rexx

 

Re: Contention for PDS after executing Rexx

Postby mvmanish » Sat Feb 04, 2017 2:09 am

Pedro wrote:Use TSO ISRDDN to see your allocations. Perhaps you have the same data set allocated by a different DD name.



Thank you Pedro. This made me to think why it has got two DD names in allocations and changed a piece of code to overcome this issue.
mvmanish
 
Posts: 10
Joined: Fri Mar 11, 2016 1:25 am
Has thanked: 1 time
Been thanked: 0 time

Re: Contention for PDS after executing Rexx

Postby Pedro » Sat Feb 04, 2017 3:16 am

you are welcome.
Pedro Vera
User avatar
Pedro
 
Posts: 584
Joined: Thu Jul 31, 2008 9:59 pm
Location: Silicon Valley
Has thanked: 0 time
Been thanked: 41 times

Previous

Return to CLIST & REXX

 


  • Related topics
    Replies
    Views
    Last post