Re: [EXTERNAL] Re: Translating a DEVTYPE from LISTC into something usable?

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

But a few pages later in the same manual:
http://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.idai200/lcvolol.htm
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.

Bill

>Got something 
>http://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.idai200/dvtt.htm
>
>
>--
>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
>To: IBM-MAIN@LISTSERV.UA.EDU
>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
>ee...@us.ibm.com
>

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


Re: [EXTERNAL] Re: Translating a DEVTYPE from LISTC into something usable?

2016-09-22 Thread Edward Finnell
Back in the olden days we were kinda pushed into new technology trying to  
get any angle we could for VSCR with software and hardware. One of the items 
was  speed matching buffers in 3380 control unit.
Everything went fine in testing. Then someone added a pack to JES3 spool.  
Blam! When I got in the PSR was just dog cussing one of the  developers. 
Evidently there was no SMB controllers in JES3 development and  they had a fall 
thru lookup followed by a DC X'00'.
 
 
In a message dated 9/22/2016 2:13:54 P.M. Central Daylight Time,  
000a2a8c2020-dmarc-requ...@listserv.ua.edu writes:

Search  for UCBTYP.



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


Re: [EXTERNAL] Re: Translating a DEVTYPE from LISTC into something usable?

2016-09-22 Thread Tom Marchant
On Thu, 22 Sep 2016 13:51:54 -0500, Dyck, Lionel B. (TRA) wrote:

>John - thank you
>
>I gathered the 3010 for dasd and it appears that tape is a bit more 
>challenging (32, 33, 34, and 78) for the 1st 2 chars and the last 4 depend on 
>the tape device.
>
>Is there a reference for these numbers - I recall there was at one time but 
>that was in the last century.

Search for UCBTYP.

-- 
Tom Marchant

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


Re: [EXTERNAL] Re: Translating a DEVTYPE from LISTC into something usable?

2016-09-22 Thread Dyck, Lionel B. (TRA)
Got something 
http://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.idai200/dvtt.htm


--
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
To: IBM-MAIN@LISTSERV.UA.EDU
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
ee...@us.ibm.com

--
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: [EXTERNAL] Re: Translating a DEVTYPE from LISTC into something usable?

2016-09-22 Thread Dyck, Lionel B. (TRA)
John - thank you

I gathered the 3010 for dasd and it appears that tape is a bit more challenging 
(32, 33, 34, and 78) for the 1st 2 chars and the last 4 depend on the tape 
device.

Is there a reference for these numbers - I recall there was at one time but 
that was in the last century.

--
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
To: IBM-MAIN@LISTSERV.UA.EDU
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
ee...@us.ibm.com

--
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