Re: PDSE dataset rename issue

[Jesse 1 Robinson]

Thanks for the display commands. But while several responders have tried to 
diagnose the nature of OP's problem, the real problem is that deleting or 
renaming a linklist data set has always been a horrible idea regardless of its 
'E-ness'. There seems to persist the illusion that modifying a linklist dataset 
out of immediate view of LLA and XCFAS will somehow fix a problem. The answer 
for all is to rebuild the linklist with a newly-named dataset or--in the case 
of nonSMS--a newly located dataset. This tech note indicates the proper action. 

http://www-01.ibm.com/support/docview.wss?uid=isg3T1010789

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Bill Allen
Sent: Thursday, June 22, 2017 6:41 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: PDSE dataset rename issue

Try issuing the following operator command D 
SMS,PDSE1,CONNECTIONS,DSN(SYS1.SIEALNKE) to see which address spaces are 
connected to it. I received the same error on a delete of a PDSE and it was 
being held by an Initiator. 
see http://www-01.ibm.com/support/docview.wss?uid=isg3T1012811

If possible, stop the Address Spaces. Also issue the command with just PDSE.  D 
SMS,PDSE,CONNECTIONS,DSN(SYS1.SIEALNKE). On my system, the linklsted PDSE 
displays from syslog are below. Being connected to *MASTER* is the probably the 
reason you cannot delete an IPL-time LNKLST PDSE.

D SMS,PDSE1,CONNECTIONS,DSN(SYS1.SIEALNKE)  

IEF196I IEF237I 5110 ALLOCATED TO SYS00247  
IEF196I IEF285I   SYS17173.T091258.RA000.MSTJCL00.R0113017 KEPT 
IEF196I IEF285I   VOL SER NOS= M22RS1.  
IGW051I PDSE CONNECTIONS Start of Report(SMSPDSE1)
-data set name-- -vsgt---   
SYS1.SIEALNKE01-M22RS1-00010D   
--asid-- --name-- --tcb--- -open-   
  001F   LLA  007F8680 Input
PDSE CONNECTIONS End of Report(SMSPDSE1)   

D SMS,PDSE,CONNECTIONS,DSN(SYS1.SIEALNKE)  

IGW051I PDSE CONNECTIONS Start of Report(SMSPDSE )  
 IEF196I IEF237I 5110 ALLOCATED TO SYS00248   
 IEF196I IEF285I   SYS17173.T091319.RA000.MSTJCL00.R0113108 KEPT  
 IEF196I IEF285I   VOL SER NOS= M22RS1.   
-data set name-- -vsgt---   
SYS1.SIEALNKE01-M22RS1-00010D   
--asid-- --name-- --tcb--- -open-   
  0001   *MASTER*  Input
PDSE CONNECTIONS End of Report(SMSPDSE )


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDSE dataset rename issue

[Bill Allen]

Try issuing the following operator command D 
SMS,PDSE1,CONNECTIONS,DSN(SYS1.SIEALNKE) to see which address spaces are 
connected to it. I received the same error on a delete of a PDSE and it was 
being held by an Initiator. 
see http://www-01.ibm.com/support/docview.wss?uid=isg3T1012811

If possible, stop the Address Spaces. Also issue the command with just PDSE.  D 
SMS,PDSE,CONNECTIONS,DSN(SYS1.SIEALNKE). On my system, the linklsted PDSE 
displays from syslog are below. Being connected to *MASTER* is the probably the 
reason you cannot delete an IPL-time LNKLST PDSE.

D SMS,PDSE1,CONNECTIONS,DSN(SYS1.SIEALNKE)  

IEF196I IEF237I 5110 ALLOCATED TO SYS00247  
IEF196I IEF285I   SYS17173.T091258.RA000.MSTJCL00.R0113017 KEPT 
IEF196I IEF285I   VOL SER NOS= M22RS1.  
IGW051I PDSE CONNECTIONS Start of Report(SMSPDSE1)
-data set name-- -vsgt---   
SYS1.SIEALNKE01-M22RS1-00010D   
--asid-- --name-- --tcb--- -open-   
  001F   LLA  007F8680 Input
PDSE CONNECTIONS End of Report(SMSPDSE1)   

D SMS,PDSE,CONNECTIONS,DSN(SYS1.SIEALNKE)  

IGW051I PDSE CONNECTIONS Start of Report(SMSPDSE )  
 IEF196I IEF237I 5110 ALLOCATED TO SYS00248   
 IEF196I IEF285I   SYS17173.T091319.RA000.MSTJCL00.R0113108 KEPT  
 IEF196I IEF285I   VOL SER NOS= M22RS1.   
-data set name-- -vsgt---   
SYS1.SIEALNKE01-M22RS1-00010D   
--asid-- --name-- --tcb--- -open-   
  0001   *MASTER*  Input
PDSE CONNECTIONS End of Report(SMSPDSE )


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: EXTERNAL: Re: PDSE dataset rename issue

[Jerry Whitteridge]

We have a LNKPDSE0 member we execute in IEACMD00 that adds a new linklist name, 
adds the PDSE libraries to the linklist and activates the new name. All other 
tasks key through automation off of the success of that linklist name before 
starting additional tasks.

(There are some IBM required PDSE libraries we leave in the IPL linklist - but 
we don't try to do dynamic  maintenance on those and build new IPL volumes for 
those. Choice is IPL linklist or dynamic refreshes - can't do both).

Jerry Whitteridge
Manager Mainframe Systems & Storage
Albertsons - Safeway Inc.
623 869 5523
Corporate Tieline - 85523

If you feel in control
you just aren't going fast enough.



-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jesse 1 Robinson
Sent: Wednesday, June 21, 2017 2:12 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: EXTERNAL: Re: PDSE dataset rename issue

I must have snoozed through this thread in 2005 because I have no recollection. 
I trust that no linklist PDSE is desperately required before the first 'add' 
command can be executed. Where do you put them and what do they look like?

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jerry Whitteridge
Sent: Wednesday, June 21, 2017 12:24 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: EXTERNAL: Re: PDSE dataset rename issue

This reminded me of why we do NOT allow PDSE in the IPL Linklist and add them 
dynamically after IPL

Please look at

https://groups.google.com/forum/#!topic/bit.listserv.ibm-main/zY1MefkB9po

Where you will see mentioned:

Until yesterday I didn't realize a PDSE LNKLST'd at IPL could not be deleted, 
not even if removed from active LNKLST.  IBM pointed me to APARs
OW40072/OW57609/OW57671 which describe the inability to delete as a 'permanent 
restriction'.  These APARs are noted in PDSE usage Redbook, but haven't found 
any applicable info in MVS Init and Tuning.

When a LNKLST'd PDSE delete attempt, error recieved is:
  IEC614I SCRATCH FAILED - RC 008, DIAGNOSTIC INFORMATION IS (043D57D3) Chasing 
the '57D3' in DFP diagnosis shows:
  Unable to delete the data set because it's currently connected on
  this system.

It appears DFSMS does a 'global connect' for LNKLST'd PDSEs, but there is no 
'global disconnect' resource.

Peter Relson of IBM eluded to the issue on this list (June 2005), "A reason I 
did not mention PDSEs is that you cannot delete a PDSE that was in the IPL-time 
LNKLST regardless of whether it is no longer in any active LNKLST set.".


I suspect this is the OP's actual problem.

Jerry Whitteridge
Manager Mainframe Systems & Storage
Albertsons - Safeway Inc.
623 869 5523
Corporate Tieline - 85523

If you feel in control
you just aren't going fast enough.



-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Elardus Engelbrecht
Sent: Tuesday, June 20, 2017 2:25 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: EXTERNAL: Re: PDSE dataset rename issue

Ok, time for me to jump in and out, since it seemed nothing is happening...

To Venkat Kulkarni :

>... to add new SYS1.SIEKLNKE dataset into system.

Are you sure of the spelling?


>But this dataset was allocated to LLA and XCF. So, we unallocated to linklist 
>and stop LLA.

It is not enough. But see below my comments.


>After this, we tried renaming this dataset using ispf 3.4 to .old but system 
>didnt allowed and received below error.

If there is an enqueue, did you press PF01 to see who all is using it?


>IEC614I rename failed rc 08 diagnostic information 040B0426, 914

Is this the full message? if not, please post it fully from start to end and 
all lines. Also post any message(s) on the SYSLOG too.


You have gotten many replies and you also posted your answers, but I have more 
questions.

1. Did you looked EVERY WHERE that dataset is used / allocated? This includes 
your own TSO session.
2. Did you checked EVERY LPAR(s) in the SysPlex for usage by all XCFAS and LLA?
3. Do you have ALTER authority to the OLD and NEW names?
4. Do you have UPDATE access to the relevant Catalog where that entry is 
sitting?

5. There is a possibility that the dataset is cataloged, but the catalog is not 
in your system from where you tried to do the rename action.

(In other words, catalog is connected, but the catalog is managed in another 
system, meaning you could have your catalogs not setup properly across your 
sysplex.)

To highlight this, in my own two SysPlexes, we have a User Catalog which is 
shared between the two SysPlexes. RACF is setup so that ALTER is granted to one 
SysPlex on these catalog entries, but at most Update at other Sysplex to those 
same entries.

So you do the

Re: PDSE dataset rename issue

[Jesse 1 Robinson]

I must have snoozed through this thread in 2005 because I have no recollection. 
I trust that no linklist PDSE is desperately required before the first 'add' 
command can be executed. Where do you put them and what do they look like?

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jerry Whitteridge
Sent: Wednesday, June 21, 2017 12:24 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: EXTERNAL: Re: PDSE dataset rename issue

This reminded me of why we do NOT allow PDSE in the IPL Linklist and add them 
dynamically after IPL

Please look at

https://groups.google.com/forum/#!topic/bit.listserv.ibm-main/zY1MefkB9po

Where you will see mentioned:

Until yesterday I didn't realize a PDSE LNKLST'd at IPL could not be deleted, 
not even if removed from active LNKLST.  IBM pointed me to APARs
OW40072/OW57609/OW57671 which describe the inability to delete as a 'permanent 
restriction'.  These APARs are noted in PDSE usage Redbook, but haven't found 
any applicable info in MVS Init and Tuning.

When a LNKLST'd PDSE delete attempt, error recieved is:
  IEC614I SCRATCH FAILED - RC 008, DIAGNOSTIC INFORMATION IS (043D57D3) Chasing 
the '57D3' in DFP diagnosis shows:
  Unable to delete the data set because it's currently connected on
  this system.

It appears DFSMS does a 'global connect' for LNKLST'd PDSEs, but there is no 
'global disconnect' resource.

Peter Relson of IBM eluded to the issue on this list (June 2005), "A reason I 
did not mention PDSEs is that you cannot delete a PDSE that was in the IPL-time 
LNKLST regardless of whether it is no longer in any active LNKLST set.".


I suspect this is the OP's actual problem.

Jerry Whitteridge
Manager Mainframe Systems & Storage
Albertsons - Safeway Inc.
623 869 5523
Corporate Tieline - 85523

If you feel in control
you just aren't going fast enough.



-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Elardus Engelbrecht
Sent: Tuesday, June 20, 2017 2:25 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: EXTERNAL: Re: PDSE dataset rename issue

Ok, time for me to jump in and out, since it seemed nothing is happening...

To Venkat Kulkarni :

>... to add new SYS1.SIEKLNKE dataset into system.

Are you sure of the spelling?


>But this dataset was allocated to LLA and XCF. So, we unallocated to linklist 
>and stop LLA.

It is not enough. But see below my comments.


>After this, we tried renaming this dataset using ispf 3.4 to .old but system 
>didnt allowed and received below error.

If there is an enqueue, did you press PF01 to see who all is using it?


>IEC614I rename failed rc 08 diagnostic information 040B0426, 914

Is this the full message? if not, please post it fully from start to end and 
all lines. Also post any message(s) on the SYSLOG too.


You have gotten many replies and you also posted your answers, but I have more 
questions.

1. Did you looked EVERY WHERE that dataset is used / allocated? This includes 
your own TSO session.
2. Did you checked EVERY LPAR(s) in the SysPlex for usage by all XCFAS and LLA?
3. Do you have ALTER authority to the OLD and NEW names?
4. Do you have UPDATE access to the relevant Catalog where that entry is 
sitting?

5. There is a possibility that the dataset is cataloged, but the catalog is not 
in your system from where you tried to do the rename action.

(In other words, catalog is connected, but the catalog is managed in another 
system, meaning you could have your catalogs not setup properly across your 
sysplex.)

To highlight this, in my own two SysPlexes, we have a User Catalog which is 
shared between the two SysPlexes. RACF is setup so that ALTER is granted to one 
SysPlex on these catalog entries, but at most Update at other Sysplex to those 
same entries.

So you do the rename on the system where you have ALTER access and there is NO 
enqueue at all.


>... it says about required authentication issue. but I feel, i have all 
>required authority to alter this dataset.

Really? See my comments above.


>Is it something to do with using 3.4 option and system check this dataset in 
>other system master catalog and doesnt allow us to rename or some other reason.

Probably, see my comments above.


Did you tried out Lizette Koehler's suggestion?

1) Is the SYS1.SIEKLNKE currently in the LINKLST?  If so, are you just 
refreshing the library?
2) If SYS1.SIEKLNKE does not current exist, you could build a new LINKLST and 
add it to the new list.


>now, I thought of creating new dataset in different volume as current one and 
>then uncatalog the current dataset and then rename the new dataset to current 
>one. I hope this should work.

No, you said it is in another 

Re: EXTERNAL: Re: PDSE dataset rename issue

[Jerry Whitteridge]

This reminded me of why we do NOT allow PDSE in the IPL Linklist and add them 
dynamically after IPL

Please look at

https://groups.google.com/forum/#!topic/bit.listserv.ibm-main/zY1MefkB9po

Where you will see mentioned:

Until yesterday I didn't realize a PDSE LNKLST'd at IPL could not be
deleted, not even if removed from active LNKLST.  IBM pointed me to APARs
OW40072/OW57609/OW57671 which describe the inability to delete as
a 'permanent restriction'.  These APARs are noted in PDSE usage Redbook,
but haven't found any applicable info in MVS Init and Tuning.

When a LNKLST'd PDSE delete attempt, error recieved is:
  IEC614I SCRATCH FAILED - RC 008, DIAGNOSTIC INFORMATION IS (043D57D3)
Chasing the '57D3' in DFP diagnosis shows:
  Unable to delete the data set because it's currently connected on
  this system.

It appears DFSMS does a 'global connect' for LNKLST'd PDSEs, but there is
no 'global disconnect' resource.

Peter Relson of IBM eluded to the issue on this list (June 2005), "A
reason I did not mention PDSEs is that you cannot delete a PDSE that was
in the IPL-time LNKLST regardless of whether it is no longer in any active
LNKLST set.".


I suspect this is the OP's actual problem.

Jerry Whitteridge
Manager Mainframe Systems & Storage
Albertsons - Safeway Inc.
623 869 5523
Corporate Tieline - 85523

If you feel in control
you just aren't going fast enough.



-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Elardus Engelbrecht
Sent: Tuesday, June 20, 2017 2:25 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: EXTERNAL: Re: PDSE dataset rename issue

Ok, time for me to jump in and out, since it seemed nothing is happening...

To Venkat Kulkarni :

>... to add new SYS1.SIEKLNKE dataset into system.

Are you sure of the spelling?


>But this dataset was allocated to LLA and XCF. So, we unallocated to linklist 
>and stop LLA.

It is not enough. But see below my comments.


>After this, we tried renaming this dataset using ispf 3.4 to .old but system 
>didnt allowed and received below error.

If there is an enqueue, did you press PF01 to see who all is using it?


>IEC614I rename failed rc 08 diagnostic information 040B0426, 914

Is this the full message? if not, please post it fully from start to end and 
all lines. Also post any message(s) on the SYSLOG too.


You have gotten many replies and you also posted your answers, but I have more 
questions.

1. Did you looked EVERY WHERE that dataset is used / allocated? This includes 
your own TSO session.
2. Did you checked EVERY LPAR(s) in the SysPlex for usage by all XCFAS and LLA?
3. Do you have ALTER authority to the OLD and NEW names?
4. Do you have UPDATE access to the relevant Catalog where that entry is 
sitting?

5. There is a possibility that the dataset is cataloged, but the catalog is not 
in your system from where you tried to do the rename action.

(In other words, catalog is connected, but the catalog is managed in another 
system, meaning you could have your catalogs not setup properly across your 
sysplex.)

To highlight this, in my own two SysPlexes, we have a User Catalog which is 
shared between the two SysPlexes. RACF is setup so that ALTER is granted to one 
SysPlex on these catalog entries, but at most Update at other Sysplex to those 
same entries.

So you do the rename on the system where you have ALTER access and there is NO 
enqueue at all.


>... it says about required authentication issue. but I feel, i have all 
>required authority to alter this dataset.

Really? See my comments above.


>Is it something to do with using 3.4 option and system check this dataset in 
>other system master catalog and doesnt allow us to rename or some other reason.

Probably, see my comments above.


Did you tried out Lizette Koehler's suggestion?

1) Is the SYS1.SIEKLNKE currently in the LINKLST?  If so, are you just 
refreshing the library?
2) If SYS1.SIEKLNKE does not current exist, you could build a new LINKLST and 
add it to the new list.


>now, I thought of creating new dataset in different volume as current one and 
>then uncatalog the current dataset and then rename the new dataset to current 
>one. I hope this should work.

No, you said it is in another system Master Cataolg. Better check all your 
Catalog entries in all systems before proceeding. Ask your Storage Admin Team 
for assistance.


>But  I am still surprised that why after un allocating the linklist and then P 
>LLA command, system is not allowing me to rename current dataset.

I am not surprised. Did you check all LPARs and all SysPlexes where that 
dataset is used/allocated?


As Giliad Wilf said, this is a "pinned' dataset, you will have trouble renaming 
that dataset. You're better off to setup new PROGxx members with NEW names and 
IPL all and every LPARs.  In this way you can then get rid of the old name.

Thus, make a NEW copy, change your PROGxx and 

Re: PDSE dataset rename issue

[Tom Marchant]

On Tue, 20 Jun 2017 02:34:19 -0500, Giliad Wilf wrote:

>>It is not clear to me what the OP did. His description of the steps
>> that he took were not precise, and were scattered among several 
>>posts.
>>
>.
>.
>On the post opening this specific thread, venkat kulkarni said:
>"But this dataset was allocated to LLA and XCF. So, we unallocated to 
>linklist and stop LLA".
> 
>This suggests he did just that, i.e., "SETPROG LNKLST,UNALLOCATE"...

Right. It "suggests" that. Other things that he posted suggest that he 
has done everything that he needs to do to get it to work, but it didn't.

Apparently more precision is needed.

-- 
Tom Marchant

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDSE dataset rename issue

[Elardus Engelbrecht]

Ok, time for me to jump in and out, since it seemed nothing is happening...

To Venkat Kulkarni :

>... to add new SYS1.SIEKLNKE dataset into system. 

Are you sure of the spelling?


>But this dataset was allocated to LLA and XCF. So, we unallocated to linklist 
>and stop LLA. 

It is not enough. But see below my comments.


>After this, we tried renaming this dataset using ispf 3.4 to .old but system 
>didnt allowed and received below error.

If there is an enqueue, did you press PF01 to see who all is using it?


>IEC614I rename failed rc 08 diagnostic information 040B0426, 914

Is this the full message? if not, please post it fully from start to end and 
all lines. Also post any message(s) on the SYSLOG too.


You have gotten many replies and you also posted your answers, but I have more 
questions.

1. Did you looked EVERY WHERE that dataset is used / allocated? This includes 
your own TSO session.
2. Did you checked EVERY LPAR(s) in the SysPlex for usage by all XCFAS and LLA?
3. Do you have ALTER authority to the OLD and NEW names?
4. Do you have UPDATE access to the relevant Catalog where that entry is 
sitting?

5. There is a possibility that the dataset is cataloged, but the catalog is not 
in your system from where you tried to do the rename action.

(In other words, catalog is connected, but the catalog is managed in another 
system, meaning you could have your catalogs not setup properly across your 
sysplex.)

To highlight this, in my own two SysPlexes, we have a User Catalog which is 
shared between the two SysPlexes. RACF is setup so that ALTER is granted to one 
SysPlex on these catalog entries, but at most Update at other Sysplex to those 
same entries.

So you do the rename on the system where you have ALTER access and there is NO 
enqueue at all.


>... it says about required authentication issue. but I feel, i have all 
>required authority to alter this dataset.

Really? See my comments above.


>Is it something to do with using 3.4 option and system check this dataset in 
>other system master catalog and doesnt allow us to rename or some other reason.

Probably, see my comments above.


Did you tried out Lizette Koehler's suggestion?

1) Is the SYS1.SIEKLNKE currently in the LINKLST?  If so, are you just 
refreshing the library?
2) If SYS1.SIEKLNKE does not current exist, you could build a new LINKLST and 
add it to the new list.


>now, I thought of creating new dataset in different volume as current one and 
>then uncatalog the current dataset and then rename the new dataset to current 
>one. I hope this should work.

No, you said it is in another system Master Cataolg. Better check all your 
Catalog entries in all systems before proceeding. Ask your Storage Admin Team 
for assistance.


>But  I am still surprised that why after un allocating the linklist and then P 
>LLA command, system is not allowing me to rename current dataset.

I am not surprised. Did you check all LPARs and all SysPlexes where that 
dataset is used/allocated?


As Giliad Wilf said, this is a "pinned' dataset, you will have trouble renaming 
that dataset. You're better off to setup new PROGxx members with NEW names and 
IPL all and every LPARs.  In this way you can then get rid of the old name.

Thus, make a NEW copy, change your PROGxx and IPL everywhere. Then you can then 
delete/rename the old dataset.

I would advise you to really properly listen to Jim Mulder's caution. He is one 
of those IMBer you simply can't argue with...

If you are still not successfully, please tell us EVERY step you tried and 
EVERY message(s) you received.

Also, I would repeat Tom Marchant question: Why are you trying to do this? 
Perhaps there is an alternative.

Groete / Greetings
Elardus Engelbrecht

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDSE dataset rename issue

[Giliad Wilf]

On Mon, 19 Jun 2017 15:23:12 -0500, Tom Marchant  
wrote:

>On Mon, 19 Jun 2017 14:45:13 -0500, Giliad Wilf wrote:
>
>>On Sun, 18 Jun 2017 20:15:50 -0400, Jim Mulder  wrote:
>>
>>> SETPROG LNKLST,UNALLOCATE
>>>
>>> SETPROG LNKLST,ALLOCATE
>>>
>>>  Use with caution.
>>>
.
.
>> 
>>The user says he already did this, to no avail.
>
>It is not clear to me what the OP did. His description of the steps
> that he took were not precise, and were scattered among several 
>posts.
>
.
.
On the post opening this specific thread, venkat kulkarni said:
"But this dataset was allocated to LLA and XCF. So, we unallocated to 
linklist and stop LLA".
 
This suggests he did just that, i.e., "SETPROG LNKLST,UNALLOCATE"...

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDSE dataset rename issue

[Gibney, Dave]

The desire to "muck" with SYS1.SIEKLNKE (or any other linklisted (especially a 
system) dataset)  on  a running system is already scary and an indication of 
probably traveling down the wrong path :)
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Tom Marchant
> Sent: Monday, June 19, 2017 1:23 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: PDSE dataset rename issue
> 
> On Mon, 19 Jun 2017 14:45:13 -0500, Giliad Wilf wrote:
> 
> >On Sun, 18 Jun 2017 20:15:50 -0400, Jim Mulder
> <d10j...@us.ibm.com> wrote:
> >
> >> SETPROG LNKLST,UNALLOCATE
> >>
> >> SETPROG LNKLST,ALLOCATE
> >>
> >>  Use with caution.
> >>
> >>Jim Mulder z/OS Diagnosis, Design, Development, Test  IBM Corp.
> >>Poughkeepsie NY
> >>
> >
> >The user says he already did this, to no avail.
> 
> It is not clear to me what the OP did. His description of the steps  that he 
> took
> were not precise, and were scattered among several posts.
> 
> For example, he said that he tried bringing down the LPAR and doing the
> rename from another LPAR. But he didn't say what he did on the other LPAR
> to attempt to do what he wanted to do.
> 
> We would be better able to help him if he would tell us *exactly* what steps
> he took and what response he got, rather than paraphrase it. It would also be
> helpful if he would tell us WHY he wants to do this.
> 
> In any case, I am not at all sure that what he thinks he wants to do is a good
> idea, but then it is not totally clear what he wants to do either.
> 
> Is he working with an alternate RES volume? Or does he want  to rename
> SYS1.SIEKLNKE in his currently active LNKLST set, and create a new one
> containing a new SYS1.SIEKLNKE? He doesn't say.
> 
> --
> Tom Marchant
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDSE dataset rename issue

[Tom Marchant]

On Mon, 19 Jun 2017 14:45:13 -0500, Giliad Wilf wrote:

>On Sun, 18 Jun 2017 20:15:50 -0400, Jim Mulder  wrote:
>
>> SETPROG LNKLST,UNALLOCATE
>>
>> SETPROG LNKLST,ALLOCATE
>>
>>  Use with caution.
>>
>>Jim Mulder z/OS Diagnosis, Design, Development, Test  IBM Corp. 
>>Poughkeepsie NY
>>
> 
>The user says he already did this, to no avail.

It is not clear to me what the OP did. His description of the steps
 that he took were not precise, and were scattered among several 
posts.

For example, he said that he tried bringing down the LPAR and 
doing the rename from another LPAR. But he didn't say what he 
did on the other LPAR to attempt to do what he wanted to do.

We would be better able to help him if he would tell us *exactly* 
what steps he took and what response he got, rather than 
paraphrase it. It would also be helpful if he would tell us WHY 
he wants to do this.

In any case, I am not at all sure that what he thinks he wants 
to do is a good idea, but then it is not totally clear what he wants 
to do either.

Is he working with an alternate RES volume? Or does he want  to 
rename SYS1.SIEKLNKE in his currently active LNKLST set, and 
create a new one containing a new SYS1.SIEKLNKE? He doesn't 
say.

-- 
Tom Marchant

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDSE dataset rename issue

[Giliad Wilf]

On Sun, 18 Jun 2017 20:15:50 -0400, Jim Mulder  wrote:

> SETPROG LNKLST,UNALLOCATE
>
> SETPROG LNKLST,ALLOCATE
>
>  Use with caution.
>
>Jim Mulder z/OS Diagnosis, Design, Development, Test  IBM Corp. 
>Poughkeepsie NY
>
 
The user says he already did this, to no avail.
 
But here is something I saw in the past for MSGIEC614I RC8 on RENAME:
 
User was attempting to RENAME a dataset covered by a generic RACF 
profile to a name not covered by a generic RACF profile.
 
The discussion there said RACF will not allow this since it would allow
the user to unprotect the dataset.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDSE dataset rename issue

[Jim Mulder]

 SETPROG LNKLST,UNALLOCATE

 SETPROG LNKLST,ALLOCATE

  Use with caution.

Jim Mulder z/OS Diagnosis, Design, Development, Test  IBM Corp. 
Poughkeepsie NY

IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> wrote on 
06/18/2017 12:17:30 PM:

> From: Giliad Wilf <00d50942efa9-dmarc-requ...@listserv.ua.edu>
> To: IBM-MAIN@LISTSERV.UA.EDU
> Date: 06/18/2017 08:13 PM
> Subject: Re: PDSE dataset rename issue
> Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU>
> 
> On Sat, 17 Jun 2017 10:45:25 +0300, venkat kulkarni 
> <venkatkulkarn...@gmail.com> wrote:
> 
> >Hello Group,
> >We have requirement to add new SYS1.SIEKLNKE dataset into system. But 
this
> >dataset was allocated to LLA and XCF. So, we unallocated to linklist 
and
> >stop LLA. After this, we tried renaming this dataset using ispf 3.4 to 
.old
> >but system didnt allowed and received below error.
> >
> >
> >IEC614I rename failed rc 08 diagnostic information 040B0426, 914
> >
> >I am unable to find any authentication issue or any other causing this
> >problem.
> >
> >Can you please help.
> >
> 
> Are you sure it was SYS1.SIEKLNKE?
> I can't recall ever seeing SYS1.SIEKLNKE.
> However, there is a PDSE named SYS1.SIEALNKE, and it is always on 
> the linklist,
> together with SYS1.LINKLIB, SYS1.MIGLIB, SYS1.CSSLIB, and SYS1.SIEAMIGE, 
right
> after SYS1.CSSLIB, even if you did not specify any of them.
> 
> So, maybe these five special datasets are sort of "pinned" for the 
> life of the IPL, and
> the only way to fiddle with them is by including corresponding 
> SYSLIB statements for
> them in PROGxx...



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDSE dataset rename issue

[Giliad Wilf]

On Sat, 17 Jun 2017 10:45:25 +0300, venkat kulkarni 
 wrote:

>Hello Group,
>We have requirement to add new SYS1.SIEKLNKE dataset into system. But this
>dataset was allocated to LLA and XCF. So, we unallocated to linklist and
>stop LLA. After this, we tried renaming this dataset using ispf 3.4 to .old
>but system didnt allowed and received below error.
>
>
>IEC614I rename failed rc 08 diagnostic information 040B0426, 914
>
>I am unable to find any authentication issue or any other causing this
>problem.
>
>Can you please help.
>
 
Are you sure it was SYS1.SIEKLNKE?
I can't recall ever seeing SYS1.SIEKLNKE.
However, there is a PDSE named SYS1.SIEALNKE, and it is always on the linklist,
together with SYS1.LINKLIB, SYS1.MIGLIB, SYS1.CSSLIB, and SYS1.SIEAMIGE, right
after SYS1.CSSLIB, even if you did not specify any of them.
 
So, maybe these five special datasets are sort of "pinned" for the life of the 
IPL, and
the only way to fiddle with them is by including corresponding SYSLIB 
statements for
them in PROGxx...

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDSE dataset rename issue

[Paul Gilmartin]

On Sat, 17 Jun 2017 10:22:53 -0700, retired mainframer wrote:
>
>Using 3.4 to display a list of DSNs does not enqueue on any of those names.  
>Once you specify any action or command on one of the DSNs displayed, enqueues 
>are probably issued for that DSN at that time.
> 
And if the data set is migrated it will probably be recalled.  Unless the action
is Delete.

Is bypassing recall built into IDCAMS, or is it scattered among other components
such as TSO and Initiator?

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDSE dataset rename issue

[retired mainframer]

Do the D command from the LPAR you are issuing the rename command from.  That 
is where the enqueue is failing.

Using 3.4 to display a list of DSNs does not enqueue on any of those names.  
Once you specify any action or command on one of the DSNs displayed, enqueues 
are probably issued for that DSN at that time.

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of venkat kulkarni
> Sent: Saturday, June 17, 2017 7:02 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: PDSE dataset rename issue
> 
> I used below command
> 
> D GRS,RES=(*,SYS1.SIEKLNKE)
> 
>  to check the current enqueue and its been used by XCFAS and LLA. and i
> tried to bring down even LPAR and tried renaming this dataset from other
> LPAR but still no success.
> 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDSE dataset rename issue

[venkat kulkarni]

I used below command

D GRS,RES=(*,SYS1.SIEKLNKE)

 to check the current enqueue and its been used by XCFAS and LLA. and i
tried to bring down even LPAR and tried renaming this dataset from other
LPAR but still no success.


On Sat, Jun 17, 2017 at 5:00 PM, venkat kulkarni <venkatkulkarn...@gmail.com
> wrote:

> i used below command
>
>
> On Sat, Jun 17, 2017 at 4:44 PM, Dan Little <dwlit...@gmail.com> wrote:
>
>> Do you mean SYS1.SIEALNKE? The return code you are getting means it is
>> enqueued.
>>
>> Validate DADSM RENAME request; enqueue on SYSDSN failed.
>>
>> On Jun 17, 2017, 09:29 -0400, Lizette Koehler <stars...@mindspring.com>,
>> wrote:
>> > A thought or two
>> >
>> > 1) Is the SYS1.SIEKLNKE currently in the LINKLST? If so, are you just
>> refreshing the library?
>> > 2) If SYS1.SIEKLNKE does not current exist, you could build a new
>> LINKLST and add it to the new list.
>> >
>> > In case one, you can use a utility like PDSCLEAN from the CBTTAPE.ORG
>> to empty the current library. Then copy the modules into the cleaned out
>> library. Then issue a F LLA,UPDATE command (Check out the syntax)
>> >
>> > In case two, there are many examples in the archives of how to build a
>> new Linklst.
>> >
>> > D GRS,RES=(*,SYS1.SIEKLNKE) will list enqueues for this file.
>> >
>> >
>> >
>> > Lizette
>> >
>> >
>> > > -Original Message-
>> > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
>> On
>> > > Behalf Of venkat kulkarni
>> > > Sent: Saturday, June 17, 2017 12:45 AM
>> > > To: IBM-MAIN@LISTSERV.UA.EDU
>> > > Subject: PDSE dataset rename issue
>> > >
>> > > Hello Group,
>> > > We have requirement to add new SYS1.SIEKLNKE dataset into system. But
>> this
>> > > dataset was allocated to LLA and XCF. So, we unallocated to linklist
>> and stop
>> > > LLA. After this, we tried renaming this dataset using ispf 3.4 to
>> .old but
>> > > system didnt allowed and received below error.
>> > >
>> > >
>> > > IEC614I rename failed rc 08 diagnostic information 040B0426, 914
>> > >
>> > > I am unable to find any authentication issue or any other causing this
>> > > problem.
>> > >
>> > > Can you please help.
>> > >
>> > >
>> >
>> > --
>> > For IBM-MAIN subscribe / signoff / archive access instructions,
>> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>
>
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDSE dataset rename issue

[venkat kulkarni]

i used below command


On Sat, Jun 17, 2017 at 4:44 PM, Dan Little <dwlit...@gmail.com> wrote:

> Do you mean SYS1.SIEALNKE? The return code you are getting means it is
> enqueued.
>
> Validate DADSM RENAME request; enqueue on SYSDSN failed.
>
> On Jun 17, 2017, 09:29 -0400, Lizette Koehler <stars...@mindspring.com>,
> wrote:
> > A thought or two
> >
> > 1) Is the SYS1.SIEKLNKE currently in the LINKLST? If so, are you just
> refreshing the library?
> > 2) If SYS1.SIEKLNKE does not current exist, you could build a new
> LINKLST and add it to the new list.
> >
> > In case one, you can use a utility like PDSCLEAN from the CBTTAPE.ORG
> to empty the current library. Then copy the modules into the cleaned out
> library. Then issue a F LLA,UPDATE command (Check out the syntax)
> >
> > In case two, there are many examples in the archives of how to build a
> new Linklst.
> >
> > D GRS,RES=(*,SYS1.SIEKLNKE) will list enqueues for this file.
> >
> >
> >
> > Lizette
> >
> >
> > > -Original Message-
> > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On
> > > Behalf Of venkat kulkarni
> > > Sent: Saturday, June 17, 2017 12:45 AM
> > > To: IBM-MAIN@LISTSERV.UA.EDU
> > > Subject: PDSE dataset rename issue
> > >
> > > Hello Group,
> > > We have requirement to add new SYS1.SIEKLNKE dataset into system. But
> this
> > > dataset was allocated to LLA and XCF. So, we unallocated to linklist
> and stop
> > > LLA. After this, we tried renaming this dataset using ispf 3.4 to .old
> but
> > > system didnt allowed and received below error.
> > >
> > >
> > > IEC614I rename failed rc 08 diagnostic information 040B0426, 914
> > >
> > > I am unable to find any authentication issue or any other causing this
> > > problem.
> > >
> > > Can you please help.
> > >
> > >
> >
> > --
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDSE dataset rename issue

[venkat kulkarni]

SYS1.SIEKLNKE  is part of link list and apf authorized library and used by
XCFAS and LLA.

To rename it, we un allocated the linklist and then P LLA and then tried
renaming the dataset but stilll getting same issue.
now, I thought of creating new dataset in different volume as current one
and then uncatalog the current dataset and then rename the new dataset to
current one. I hope this should work.

But  I am still surprised that why after un allocating the linklist and
then P LLA command, system is not allowing me to rename current dataset.


please suggest.

On Sat, Jun 17, 2017 at 4:29 PM, Lizette Koehler <stars...@mindspring.com>
wrote:

> A thought or two
>
> 1) Is the SYS1.SIEKLNKE currently in the LINKLST?  If so, are you just
> refreshing the library?
> 2) If SYS1.SIEKLNKE does not current exist, you could build a new LINKLST
> and add it to the new list.
>
> In case one, you can use a utility like PDSCLEAN from the CBTTAPE.ORG to
> empty the current library.  Then copy the modules into the cleaned out
> library.  Then issue a F LLA,UPDATE command (Check out the syntax)
>
> In case two, there are many examples in the archives of how to build a new
> Linklst.
>
> D GRS,RES=(*,SYS1.SIEKLNKE)will list enqueues  for this file.
>
>
>
> Lizette
>
>
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> > Behalf Of venkat kulkarni
> > Sent: Saturday, June 17, 2017 12:45 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: PDSE dataset rename issue
> >
> > Hello Group,
> > We have requirement to add new SYS1.SIEKLNKE dataset into system. But
> this
> > dataset was allocated to LLA and XCF. So, we unallocated to linklist and
> stop
> > LLA. After this, we tried renaming this dataset using ispf 3.4 to .old
> but
> > system didnt allowed and received below error.
> >
> >
> > IEC614I rename failed rc 08 diagnostic information 040B0426, 914
> >
> > I am unable to find any authentication issue or any other causing this
> > problem.
> >
> > Can you please help.
> >
> >
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDSE dataset rename issue

[Dan Little]

Do you mean SYS1.SIEALNKE? The return code you are getting means it is enqueued.

Validate DADSM RENAME request; enqueue on SYSDSN failed.

On Jun 17, 2017, 09:29 -0400, Lizette Koehler <stars...@mindspring.com>, wrote:
> A thought or two
>
> 1) Is the SYS1.SIEKLNKE currently in the LINKLST? If so, are you just 
> refreshing the library?
> 2) If SYS1.SIEKLNKE does not current exist, you could build a new LINKLST and 
> add it to the new list.
>
> In case one, you can use a utility like PDSCLEAN from the CBTTAPE.ORG to 
> empty the current library. Then copy the modules into the cleaned out 
> library. Then issue a F LLA,UPDATE command (Check out the syntax)
>
> In case two, there are many examples in the archives of how to build a new 
> Linklst.
>
> D GRS,RES=(*,SYS1.SIEKLNKE) will list enqueues for this file.
>
>
>
> Lizette
>
>
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> > Behalf Of venkat kulkarni
> > Sent: Saturday, June 17, 2017 12:45 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: PDSE dataset rename issue
> >
> > Hello Group,
> > We have requirement to add new SYS1.SIEKLNKE dataset into system. But this
> > dataset was allocated to LLA and XCF. So, we unallocated to linklist and 
> > stop
> > LLA. After this, we tried renaming this dataset using ispf 3.4 to .old but
> > system didnt allowed and received below error.
> >
> >
> > IEC614I rename failed rc 08 diagnostic information 040B0426, 914
> >
> > I am unable to find any authentication issue or any other causing this
> > problem.
> >
> > Can you please help.
> >
> >
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDSE dataset rename issue

[Lizette Koehler]

A thought or two

1) Is the SYS1.SIEKLNKE currently in the LINKLST?  If so, are you just 
refreshing the library?
2) If SYS1.SIEKLNKE does not current exist, you could build a new LINKLST and 
add it to the new list.

In case one, you can use a utility like PDSCLEAN from the CBTTAPE.ORG to empty 
the current library.  Then copy the modules into the cleaned out library.  Then 
issue a F LLA,UPDATE command (Check out the syntax)

In case two, there are many examples in the archives of how to build a new 
Linklst.

D GRS,RES=(*,SYS1.SIEKLNKE)will list enqueues  for this file.



Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of venkat kulkarni
> Sent: Saturday, June 17, 2017 12:45 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: PDSE dataset rename issue
> 
> Hello Group,
> We have requirement to add new SYS1.SIEKLNKE dataset into system. But this
> dataset was allocated to LLA and XCF. So, we unallocated to linklist and stop
> LLA. After this, we tried renaming this dataset using ispf 3.4 to .old but
> system didnt allowed and received below error.
> 
> 
> IEC614I rename failed rc 08 diagnostic information 040B0426, 914
> 
> I am unable to find any authentication issue or any other causing this
> problem.
> 
> Can you please help.
> 
> 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDSE dataset rename issue

[venkat kulkarni]

Thanks for reply. I looked at other google for this error and it says about
required authentication issue. but I feel, i have all required authority to
alter this dataset.

Is it something to do with using 3.4 option and system check this dataset
in other system master catalog and doesnt allow us to rename or some other
reason.

On Sat, Jun 17, 2017 at 11:25 AM, retired mainframer <
retired-mainfra...@q.com> wrote:

> Look at your DFSMSdfp Diagnosis manual in the DADSM RENAME Return and
> Diagnostic Codes section.  It says the enqueue failed.
>
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> > Behalf Of venkat kulkarni
> > Sent: Saturday, June 17, 2017 12:45 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: PDSE dataset rename issue
> >
> > Hello Group,
> > We have requirement to add new SYS1.SIEKLNKE dataset into system. But
> this
> > dataset was allocated to LLA and XCF. So, we unallocated to linklist and
> > stop LLA. After this, we tried renaming this dataset using ispf 3.4 to
> .old
> > but system didnt allowed and received below error.
> >
> >
> > IEC614I rename failed rc 08 diagnostic information 040B0426, 914
> >
> > I am unable to find any authentication issue or any other causing this
> > problem.
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDSE dataset rename issue

[venkat kulkarni]

no, its not in sysplex.. just volumes are shared.. i tried shutting down
the system and tired to rename from other system also. but getting similar
issue .

On Sat, Jun 17, 2017 at 12:03 PM, Lucas Rosalen 
wrote:

> Maybe this dataset is allocated by XCF and LLA in another system of the
> sysplex, you might wanna check that.
>
> Lucas
>
> On Jun 17, 2017 10:53, "Edward Finnell" <
> 000248cce9f3-dmarc-requ...@listserv.ua.edu> wrote:
>
> >
> > Example 2:
> > To  display resource information about all resources whose major name is
> > SYSDSN,  enter:
> > D GRS,RES=(SYSDSN,*)
> >
> >
> >
> >
> > In a message dated 6/17/2017 3:25:49 A.M. Central Daylight Time,
> > retired-mainfra...@q.com writes:
> >
> > Look at  your DFSMSdfp Diagnosis manual in the DADSM RENAME Return and
> > Diagnostic Codes  section.  It says the enqueue  failed.
> >
> >
> >
> > --
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> >
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDSE dataset rename issue

[Lucas Rosalen]

Maybe this dataset is allocated by XCF and LLA in another system of the
sysplex, you might wanna check that.

Lucas

On Jun 17, 2017 10:53, "Edward Finnell" <
000248cce9f3-dmarc-requ...@listserv.ua.edu> wrote:

>
> Example 2:
> To  display resource information about all resources whose major name is
> SYSDSN,  enter:
> D GRS,RES=(SYSDSN,*)
>
>
>
>
> In a message dated 6/17/2017 3:25:49 A.M. Central Daylight Time,
> retired-mainfra...@q.com writes:
>
> Look at  your DFSMSdfp Diagnosis manual in the DADSM RENAME Return and
> Diagnostic Codes  section.  It says the enqueue  failed.
>
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDSE dataset rename issue

[Edward Finnell]

 
Example 2: 
To  display resource information about all resources whose major name is 
SYSDSN,  enter:
D GRS,RES=(SYSDSN,*)


 
 
In a message dated 6/17/2017 3:25:49 A.M. Central Daylight Time,  
retired-mainfra...@q.com writes:

Look at  your DFSMSdfp Diagnosis manual in the DADSM RENAME Return and 
Diagnostic Codes  section.  It says the enqueue  failed.



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDSE dataset rename issue

[retired mainframer]

Look at your DFSMSdfp Diagnosis manual in the DADSM RENAME Return and 
Diagnostic Codes section.  It says the enqueue failed.

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of venkat kulkarni
> Sent: Saturday, June 17, 2017 12:45 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: PDSE dataset rename issue
> 
> Hello Group,
> We have requirement to add new SYS1.SIEKLNKE dataset into system. But this
> dataset was allocated to LLA and XCF. So, we unallocated to linklist and
> stop LLA. After this, we tried renaming this dataset using ispf 3.4 to .old
> but system didnt allowed and received below error.
> 
> 
> IEC614I rename failed rc 08 diagnostic information 040B0426, 914
> 
> I am unable to find any authentication issue or any other causing this
> problem.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

PDSE dataset rename issue

[venkat kulkarni]

Hello Group,
We have requirement to add new SYS1.SIEKLNKE dataset into system. But this
dataset was allocated to LLA and XCF. So, we unallocated to linklist and
stop LLA. After this, we tried renaming this dataset using ispf 3.4 to .old
but system didnt allowed and received below error.


IEC614I rename failed rc 08 diagnostic information 040B0426, 914

I am unable to find any authentication issue or any other causing this
problem.

Can you please help.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN