005 7:09 AM
>To: IBM-MAIN@BAMA.UA.EDU
>Subject: Re: ESOTERIC decomissioning
>
>On Wed, 16 Nov 2005 17:16:58 -0600, Big Iron
><[EMAIL PROTECTED]>
>wrote:
>
>>
>>The problem with esoterics in the catalog is that there is a sequence
>>number included in the de
ECTED] On
Behalf Of Mark Zelden
Sent: Thursday, November 17, 2005 7:09 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: ESOTERIC decomissioning
On Wed, 16 Nov 2005 17:16:58 -0600, Big Iron
<[EMAIL PROTECTED]>
wrote:
>
>The problem with esoterics in the catalog is that there is a sequence
>nu
On Wed, 16 Nov 2005 17:16:58 -0600, Big Iron <[EMAIL PROTECTED]>
wrote:
>
>The problem with esoterics in the catalog is that there is a
>sequence number
>included in the device type entry, so if you remove one, all the other ones
>with larger sequence numbers will change; so if there are esoterics
At 17:16 -0600 on 11/16/2005, Big Iron wrote about ESOTERIC decomissioning:
The problem with esoterics in the catalog is that there is a sequence number
included in the device type entry, so if you remove one, all the other ones
with larger sequence numbers will change; so if there are
There is the utility IEFESO in SAMPLIB, in conjunction with the member
IEFESOJL.
You can modify the asm code to your liking. We did some very basic
changes to it to get what we wanted.
I ended up with a report like this:
Data set FAC.CB.CH.CIMSDISK.BKPOCT03 was found to be
cata
You can find entries in a catalog that specify an esoteric. They look like
x'8000' (tape) or x'2000' (disk) where is a binary sequence number.
Other than say JES2 EXIT 6 or something similar, it would be harder to
identify jobs that specify an esoteric. A batch job will JCL error if i
6 matches
Mail list logo
