On Thu, 22 Sep 2016 13:53:39 -0500, Dyck, Lionel B. (TRA) wrote:

But a few pages later in the same manual:
some of the examples have 3030200E, which means the shared DASD bit was set in 
the UCB when the catalog entry was created. That's not shown in the table. 
You'll want to check for that too.


>Got something 
>Lionel B. Dyck (TRA Contractor)
>Mainframe Systems Programmer 
>Enterprise Infrastructure Support (Station 200) (005OP6.3.10)
>VA OI&T Service Delivery & Engineering
>-----Original Message-----
>From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
>Behalf Of John Eells
>Sent: Thursday, September 22, 2016 1:48 PM
>Subject: [EXTERNAL] Re: Translating a DEVTYPE from LISTC into something usable?
>Some other trivia about DEVTYPE in catalog entries...
>The first two bytes are "feature" bits.  For modern disk, it will always be 
>x'3010'.  These bits represent obsolete and now-standard functions that were 
>once features, namely burst mode (obsolete), data chaining (now standard), and 
>rotational position sensing (now both standard *and* obsolete!).
>The next byte is the device class, x'20' for direct access.
>The last byte, represents the device, and as others have posted x'0F' is set 
>for 3390.
>(Wayne Rhoten had the feature bit mapping when I looked for this a couple 
>months back!)
>John Eells
>IBM Poughkeepsie

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

Reply via email to