Re: PDSE supported for product dataset z/OS version

Peter Relson wrote: >Jim Mulder pointed out to me that the PROGxx documentation is incorrect in >having failed to delete a relevant statement. >What is there and correct (under "using the LPA statement") >Use the LPA statement to specify: >-- Modules that are to be added to the LPA at the end

Re: PDSE supported for product dataset z/OS version

> Does this imply that program objects can never be in LPA, not merely > that such objects can't be accessed until late in the IPL processing? No. At least "no" based on the meaning of LPA. But perhaps you meant PLPA. > Does that imply that soon COBOL programs will not be eligible for LPA? No.

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

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

Re: z/OS TCP/IP question: name resolution order/override

Charles Mills wrote: > Do you "own" the target host? Can you issue your own SSL/TLS server certificate? >Because you can issue a certificate for an IP address as well as for a name (or for both one or two names and one or two addresses). Cute feature: with a name, you can wildcard the high order

Help with MQ and MA10: MQ Series for MVS/ESA ISPF Utilities

Dear Group, I am trying to get the ISPF based tool MQDLQ to work with MQ V8. The program MQDLQ0 is part of MA10 and wants a Queue Manager name as input. I have tried ISPF PARM and ISPF VPUT. Does anyone have MQDLQ working from a panel that supplies the Queue Manager Name? @MQ EXEC

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

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

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

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 -

Re: SYSZMCS Hang

OMG Human Error! In a message dated 9/22/2016 4:31:43 A.M. Central Daylight Time, robert.richa...@opm.gov writes: Did not need to go that far. It is believed that the issue was caused by a series of errant VTAM commands issued by a sysprog on the wrong system.

Re: Translating a DEVTYPE from LISTC into something usable?

This table from MXG should cover most device mappings: /* COPYRIGHT (C) 1985,2015 BY MERRILL CONSULTANTS DALLAS TEXAS */ /* LAST UPDATED: OCT 15, 2015. CHANGE 33.249. */ /*/ /*** VMACUCB INCLUDED CODE

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

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)

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

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.

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

Re: Translating a DEVTYPE from LISTC into something usable?

EXCELLENT - Thank you -- Lionel B. Dyck (TRA Contractor) Mainframe Systems Programmer Enterprise Infrastructure Support (Station 200) (005OP6.3.10) VA OI Service Delivery & Engineering -Original Message- From: IBM

Re: PDSE supported for product dataset z/OS version

Paul Gilmartin wrote: On Thu, 22 Sep 2016 12:59:53 -0400, John Eells wrote: ..., but the reason why you can't use PDSEs early in IPL processing (think "parmlib concatenation or LPA list") is more prosaic. Much of the code needed to process PDSEs lives in LPA. Until CLPA is done, they cannot

Re: Translating a DEVTYPE from LISTC into something usable?

How about this.. /* "convert" DEVTYPE code to something that we can read */ /* Yes there are a few codes that are for really "old" devices */ SELECT WHEN DEVTYPE = '30102004' THEN DEVMODEL = 'DISK-9345

Re: PDSE supported for product dataset z/OS version

On Thu, 22 Sep 2016 12:59:53 -0400, John Eells wrote: > >..., but the reason why you can't use PDSEs early in IPL processing >(think "parmlib concatenation or LPA list") is more prosaic. Much of >the code needed to process PDSEs lives in LPA. Until CLPA is done, they >cannot be opened. > Does

Re: Translating a DEVTYPE from LISTC into something usable?

Thank you - I can use this as the start for my rexx code to do it Have a great rest of the week/weekend. -- Lionel B. Dyck (TRA Contractor) Mainframe Systems Programmer Enterprise Infrastructure Support (Station 200)

Re: Translating a DEVTYPE from LISTC into something usable?

Lionel, I wrote an assembler macro several years ago. Needless to say I haven't updated it since 1994. May not be complete but it's a place to start. MACRO DEVICES *** *

Re: Translating a DEVTYPE from LISTC into something usable?

I haven't looked, but maybe the UCB mapping macro. Dyck, Lionel B. (TRA) September 22, 2016 at 1:08 PM Does anyone have any suggestions (or code) that will convert the DEVTYPE returned from a LISTC into something meaningful to a human? For example a LISTC for a

PDSE, also have MVS recognize FBA disk was Re: PDSE supported for product dataset z/OS version

[Default] On 22 Sep 2016 09:59:39 -0700, in bit.listserv.ibm-main ee...@us.ibm.com (John Eells) wrote: >Jesse 1 Robinson wrote: >> Just keep in mind that AFAIK opening a PDSE still requires SMS to be active. >> That means that certain libraries opened very early in IPL must still be >> standard

Re: HSM EXPIRE NON-USAGE reporting

CBTTAPE File 047 File 134 The descriptions do not describe exactly what are wanting, but it could be good start. Al Nims Systems Admin/Programmer 3 UFIT University of Florida (352) 273-1298 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On

Translating a DEVTYPE from LISTC into something usable?

Does anyone have any suggestions (or code) that will convert the DEVTYPE returned from a LISTC into something meaningful to a human? For example a LISTC for a disk dataset returned DEVTYPE--X'3010200F' This is most likely a 3390 but that is just a guess as it is on disk. Thanks

HSM EXPIRE NON-USAGE reporting

We have a business situation where I need to create a report (i.e. monthly) for end users that shows which datasets that HSM will expire on future dates, based on EXPIRE NON-USAGE vs LAST REF. As an example, a report run on Oct 1st would list all datasets that would get deleted sometime

Re: PDSE supported for product dataset z/OS version

Jesse 1 Robinson wrote: Just keep in mind that AFAIK opening a PDSE still requires SMS to be active. That means that certain libraries opened very early in IPL must still be standard PO. I don't recall whether SMS must be active to open a PDSE (managed or not), but the reason why you can't

Re: SYSZMCS Hang

> On Sep 22, 2016, at 2:23 AM, Elardus Engelbrecht > wrote: > > Edward Finnell wrote: > >> EREP show anything on the offending LPAR? > > What type of EREP records will be written if there are such events? EOD? OBR? > SFT? or other type? > > Or should I just

Cobol 5 compile parameters

Firstly, I think you have posted this in the "google groups" for IBM-MAIN. That is not the best way to do it, as many can't see your post as it is not propagated from there to the actual LISTSERV. You need to subscribe to the IBM-MAIN list to get the most benefit. Search hear, or elsewhere, for

Re: z/OS TCP/IP question: name resolution order/override

> No, it's an SSL (TLS) connection. Need to address by hostname. Do you "own" the target host? Can you issue your own SSL/TLS server certificate? Because you can issue a certificate for an IP address as well as for a name (or for both one or two names and one or two addresses). Cute feature:

Re: PDSE supported for product dataset z/OS version

Just keep in mind that AFAIK opening a PDSE still requires SMS to be active. That means that certain libraries opened very early in IPL must still be standard PO. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595

Re: PDSE supported for product dataset z/OS version

Radoslaw Skorupka wrote: >It was 25 years ago. Things changed. Indeed. >Nowadays the most popular way to destroy PDSE is to share it across sysplexes. Or using undocumented or wrong system services to use them... If you do those stunts across sysplexes, I'm running away. >People who are

Re: PDSE supported for product dataset z/OS version

W dniu 2016-09-22 o 15:36, Joel C. Ewing pisze: On 09/22/2016 07:30 AM, Tom Marchant wrote: On Thu, 22 Sep 2016 13:48:42 +0200, R.S. wrote: PDSEs were available long before z/OS brandname was born. Executable code could be stored in PDSE starting with MVS 4.3 in

Re: PDSE supported for product dataset z/OS version

On 09/22/2016 07:30 AM, Tom Marchant wrote: > On Thu, 22 Sep 2016 13:48:42 +0200, R.S. > wrote: > >> PDSEs were available long before z/OS brandname was born. > Executable code could be stored in PDSE starting with MVS 4.3 in 1992. > From the General Information

Re: PDSE supported for product dataset z/OS version

On Thu, 22 Sep 2016 13:48:42 +0200, R.S. wrote: >PDSEs were available long before z/OS brandname was born. Executable code could be stored in PDSE starting with MVS 4.3 in 1992. From the General Information manual: Additional MVS/ESA SP 4.3 support with

Re: SYSZMCS Hang

If that is the case, you may have been able to save yourself an IPL using the CMDS console command that allows for cancelling in-process/hung operator commands. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President

Re: PDSE supported for product dataset z/OS version

W dniu 2016-09-22 o 13:43, Nathan Astle pisze: Hello, Are there any information starting from which version of z/OS, the Product load modules datasets can be created as PDSE ? 1.1 PDSEs were available long before z/OS brandname was born. -- Radoslaw Skorupka Lodz, Poland --- Treść tej

PDSE supported for product dataset z/OS version

Hello, Are there any information starting from which version of z/OS, the Product load modules datasets can be created as PDSE ? Nathan -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to

RFE to consider - Support to convert GDG to Extended

I didn't write this RFE but just found it and fully support it. It requests IBM to provide the ability to convert an existing GDG to an Extended GDG. The url is: http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe_ID=69672 Please add your vote to this and let's "nudge" IBM to

Re: SYSZMCS Hang

Did not need to go that far. It is believed that the issue was caused by a series of errant VTAM commands issued by a sysprog on the wrong system. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edward Finnell Sent: Wednesday,

Re: SYSZMCS Hang

Edward Finnell wrote: >The Sample EREP report covers about everything. Think it's a nine step job. >May have to add parms for devices or ranges. Generally look for the outliers >perm, temp and soft just to get in the ball park. If no SAD were taken might >get the abending task and go from

Re: SYSZMCS Hang

The Sample EREP report covers about everything. Think it's a nine step job. May have to add parms for devices or ranges. Generally look for the outliers perm, temp and soft just to get in the ball park. If no SAD were taken might get the abending task and go from there.. In a message

Re: SYSZMCS Hang

Edward Finnell wrote: >EREP show anything on the offending LPAR? What type of EREP records will be written if there are such events? EOD? OBR? SFT? or other type? Or should I just use PRINT=AL and the scan the output? TIA! Groete / Greetings Elardus Engelbrecht