Re: PDSE V2 data set info

It IS available, apparently, for a fee. Speak with your friendly IBM rep. And yes, if this answer makes you go "gr" then trust me, you are not alone. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Smith Sent:

Re: Rexx or similar to clone a RACF user?

Ituriel, Very clever. However, I recommend using the 0203 record for group connections instead of the 0102 record. If the user is connected to a UNIVERSAL group, there won't be a 0102 record unless the user has an authority greater than USE. Regards, Bob Robert S. Hansel Lead RACF Specialist

Re: PDSE V2 data set info

This question has come up before. The programmatic interface is through something called FAMS, and it is not publicly available. sas On Tue, Jan 28, 2020 at 5:49 AM Robin Atwood wrote: > I have a requirement in my queue to include the PDSE Version and the MAXGEN > limit in the DSINFO report

PDSE V2 data set info

I have a requirement in my queue to include the PDSE Version and the MAXGEN limit in the DSINFO report our server sends to workstation clients. I checked the F1 DSCB, IGGCSI00 output fields, SMDEs and found nothing. Searching only produced Lionel Dyck's PGSEGEN utility but that works in an ISPF

Re: Connect upgrade Secure+ requirement

HCR77A0 is the minimum supported ICSF version on z/OS 1.13 for connect 5.2. As to installing without SMP/E ... thats a head scratcher. I would not just copy the libraries from z/OS 2.1 ... I would see if IBM can make you a tape. Joe On Tue, Jan 28, 2020 at 6:27 AM Steve David wrote: > Thank

Re: Connect upgrade Secure+ requirement

Thank you Joe , so FMID HCR77A0 comes with zOS V2.1 base works well with zOS 1.13..? Since we don't have working SMPE environment in zOS 1.13, is it ok to copy CSF libraries from zOS V2.1 ? Actually we have CSF.** libraries available on 1.13 as well,but not sure whether ICSF will support CD V5.2

Re: PDSE V2 data set info

In SMF 14/15, there is a field SMF14DSNVER which will tell you the PDSE version... Joe On Tue, Jan 28, 2020 at 5:40 AM Greg Price wrote: > Hi Robin, > > I'm sure others will jump in if I am not up to date, but AFAIK, you > cannot get these pieces of information without opening the data set and

Re: Connect upgrade Secure+ requirement

This will tell you: https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.2.0/com.ibm.zos.v2r2.csfb200/csffmid.htm You need FMID HCR77A0 or above. Joe On Mon, Jan 27, 2020 at 11:11 PM Steve David wrote: > Hi All, > > We are upgrading CD from V4.8 to V5.2, currently running in zOS 1.13, but

ISPF Developer Tips & Techniques 1.6 available

Go to www.lbdsoftware.com for version 1.6 of the ISPF Developer Tips and Tricks. Here are the most recent three updates: Version 1.6 26 January 2020 1. Update PNREXX to use 4 digit year and routine to insert commas for long numbers (thx to Doug Nadel)

Re: PDSE V2 data set info

Hi Robin, I'm sure others will jump in if I am not up to date, but AFAIK, you cannot get these pieces of information without opening the data set and issuing a ISITMGD macro. A few folks have opined that it should be possible to acquire this data without an OPEN, but it remains as it was.

Re: Connect upgrade Secure+ requirement

We have load module of ICSF but we don't have smpe environment to determine its level. Is there a way to print any load module and see the details like any eyecatcher ? Thanks Steve On Tuesday, 28 January 2020, Joe Monk wrote: > HCR77A0 is the minimum supported ICSF version on z/OS 1.13 for

Re: Connect upgrade Secure+ requirement

You will want to look at the program directory for requirements, but who says you cannot create your own smpe environment for CSF? Other than the job to allocate the CSI itself, all the rest of the needed jobs are in SYS1.SAMPLIB to allocate the files, add EF's, etc. I don’t even want to

Re: Prolog code of Metal C program (register 0)

Well you're right, but I wasn't even thinking of that aspect. I was just thinking of "why 64-bit?" I would think you ought to be able to safely guess you could do a 30MB GETMAIN in 31-bit private. If every assembler statement generates 1000 bytes of ADATA, or rather, ADATA that you need to

Re: Connect upgrade Secure+ requirement

There is a member in SYS1.SAMPLIB named GIMSAMPU, that provides JCL to allocate a new CSI. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Jousma, David Sent: Tuesday, January 28, 2020 11:39 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Connect upgrade

Re: PDSE V2 data set info

One other possibility is that it is not publicly available but can be inferred from publicly available macros. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Robin Atwood Sent: Tuesday,

Re: Connect upgrade Secure+ requirement

Hi Steve, You can use the PDS Command Processor for this and a lot more. Please see cbttape.org (File 182). I would use the "HIS" (History) subcommand on the modules in question. Another possibility is use AMASPZAP to DUMP the module. Regards, Davie On 2020-01-28 13:17, Steve David wrote: > We

Re: Connect upgrade Secure+ requirement

Browse CSF.SCSFMOD0(CSFINIT) (assuming that's what the dataset is named in your environment) and perform a find on HCR. That'll show you the FMID. Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key -

Re: PDSE V2 data set info

DCOLLECT? -Original Message- From: IBM Mainframe Discussion List On Behalf Of Robin Atwood Sent: Tuesday, January 28, 2020 4:49 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: PDSE V2 data set info [CAUTION: This Email is from outside the Organization. Do not click links or open attachments

Re: TCPIP IPv6 reachability issue after link restart on VM and zLinux

I see something I should clarify directly: " I see packets going out and replies coming in - but Linux does not appear to get any traffic (RX counters not increasing)" - when I say "I see packets going out and replies coming in" that's on the switch side, not in the zLinux LPAR. On Tue, Jan 28,

TCPIP IPv6 reachability issue after link restart on VM and zLinux

Hi, I'm operating a z114 with OSA Express 4S 1G and 10G cards. I'm having the following issue on both zLinux (kernel 5.3.0) and z/VM 630. When TCPIP is restarted, either in VM as "FORCE TCPIP" + "XAUTOLOG TCPIP" (or linux as "ip link set down" followed up "up"), or a re-IPL in either OS, the IPv6

DFSort question

Hi, User ran a job the uses DFSort to copy a dataset. The output dataset is on tape. The output dataset existed on tape before the job run. Message IGD17101I was issued saying that there already was a dataset with that name. The job ended with condition code 0. Is this a DFSort behavior? If yes,

Re: PDSE V2 data set info

On 1/28/2020 5:48 AM, Robin Atwood wrote: I have a requirement in my queue to include the PDSE Version and the MAXGEN limit in the DSINFO report our server sends to workstation clients. I checked the F1 DSCB, IGGCSI00 output fields, SMDEs and found nothing. Searching only produced Lionel Dyck's

Re: PDSE V2 data set info

Thanks to everyone who replied, you have confirmed what I had suspected. The ISITMGD macro seems to do some of what I want, I will take that route. Robin -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Allan Staller Sent: 29 January

Re: DFSort question

The dataset is Not Cataloged 2. It does exist on tape and you must reference the dataset with DSN and VOLSER. Alternative is to create the tape with a different DSN so it can be cataloged. If the same VOLSER you overwrote it and any subsequent files on the tape are destroyed. Applies to real