Re: SuperWylbur Users

2020-06-29 Thread Gibney, Dave
Did you reassemble (assuming Wylbur code is available) with new JES2 macros?

> -Original Message-
> From: IBM Mainframe Discussion List  On
> Behalf Of Longnecker, Dennis
> Sent: Monday, June 29, 2020 4:16 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: SuperWylbur Users
> 
> Hello -
> Anyone here still using SuperWylbur and have it up and running on a z/OS 2.4
> system?   Bringing up 2.4 now and the JES parts aren't working correctly.
> Before I start digging into the code, I wanted to see if anyone else has 
> solved
> it.
> 
> Thanks,
> Dennis
> 
> --
> 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: AT-TLS ?

2020-06-29 Thread Rob Schramm
Redbooks are both helpful and not.
There was an old presentation on it (share) that I found really helpful and
insightful.

Do you have zosmf setup?  If not it is possible to use the samples to set
it up.



On Sun, Jun 28, 2020, 18:26 Lionel B Dyck  wrote:

> Anyone have any pointers for configuring AT-TLS on z/OS?
>
>
>
>
>
> Lionel B. Dyck <
> Website:   https://www.lbdsoftware.com
>
> "Worry more about your character than your reputation.  Character is what
> you are, reputation merely what others think you are." - John Wooden
>
>
>
>
> --
> 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: New Mainframe Community

2020-06-29 Thread Gord Tomlin

On 2020-06-26 15:21, Gord Tomlin wrote:

On 2020-06-26 12:57, Henri Kuiper wrote:
here’s a little “why” for the existence of the thing 
:https://zdevops.tumblr.com/post/620908065704853504/mainframe-community-mattermost 



I read the above, and then headed over to see https://mainframe.community/

I see that the privacy policy and terms are the default ones supplied by 
Mattermost. Has this site set up its own privacy policy and terms, or is 
it relying on the defaults provided by Mattermost? I have to ask, 
because there isn't much to see without creating an account and logging in.


I took the next step and joined this new community to see what all the 
fuss here was all about. I don't like to either boost or trash something 
that I know nothing about.


I was already familiar with Mattermost. For those who aren't, it's an 
open source package that looks and acts very much like Slack did six 
months ago. So if you know Slack, you pretty much know Mattermost.


Here's what I found, in no particular order:
- There are no ads.
- There is no sign of people selling answers
  (for clarity, the comments about those two items were about
  another site).
- I've seen no sign of pedantry.
- I haven't seen topics wander off into hardware nostalgia or, as
  in this very topic, discussions of quote marks and character sets.
- I haven't seen a lot of the key IBMers who make major contributions
  here.
- The new site appears to be somewhat more collaborative discussion, as
  opposed to Q
- I haven't seen anyone asking questions without supplying the
  information that someone would need to answer the questions.
- It's not a huge population at this point (as I write this, the
  Mattermost equivalent of Slack's #general channel  has 119 members).
- The topics discussed seem to be more "new workload" and less "legacy".
- It's a little chaotic, because the Slack/Mattermost chat-oriented
  paradigm does not really lend itself to threaded conversations.
  When it gets a lot of users, it's likely to feel a lot like the Zowe
  Slack site.
- It's just different from IBM-MAIN. As far as I can tell, it's not
  trying to replace IBM-MAIN (and if it was, the choice of a chat tool
  rather than a forum tool would have been a mistake).

--

Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer Corporation)
Tel: (905) 470-7113, Fax: (905) 470-6507
Support: https://actionsoftware.com/support/

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


Re: MVS master consoles

2020-06-29 Thread Barbara Nitz
>Hi.  I'm learning some things about MVS consoles.I have both the PD 
>console (SYSCON - aka Operating System Messages task on the HMC) and a 
>local 3270 console (named MVSMAST) active.  Both have all routing codes 
>assigned.  This is in a virtual machine, so SYSCON works with the #CP 
>VINPUT VMSG command and displays line mode output.

I am assuming that SYSCON is the operating system messages console and MVSMAST 
is the 3270 console interface that can be started on the HMC that acts like a 
traditional MVS master console. See below.

From a z/OS point of view there is no 'master console' necessary anymore. z/OS 
happily runs without any 3270 console (local non-SNA) attached these days since 
z/OS 1.6 ore 1.8 (when console restructure was done). That being said, without 
a 'channel-attached master console' the NIP messages during IPL automatically 
go to the operating system console until the point in the IPL when the console 
address space becomes active. At that point all messages are either hardcopy 
only or go to the HMCS console if it is active. I think if the HMCS is active 
at NIP that NIP messages go there instead of the SYSCON.

The 'operating system messages' console needs to be explicitly activated after 
NIP (v cn(*),activate) even if you can still see the NIP messages there. It 
should not stay active for long (v cn(*),deactivate) because it uses the SPI 
which is comparatively slow and could cause problems in the console address 
space (like WTO buffer shortages back in the days when customers were able to 
force CONSOLE to a dispatching priority of 9F instead of FF). Besides, the 
health checker will nag you to inactivate the SYSCON.

The HMCS console acts like a normal MCS console once it is opened (with a 
rather clumsy keyboard interface - the PFKEY-definitions don't really work, and 
the enter key is NOT ctrl). Closing the 3270 window will simply deactivate that 
console without any problems.

If your MASTCON is defined in CONSOLxx with a UCB number then that is a regular 
MCS console (and knowing almost nothing about VM) and acts like a 'master 
console' of old. If that console gets inactivated via some VM command, then 
z/OS will just mark it as inactive and go on it's merry way until it is 
explicitly reactivated from within z/OS (v xxx,console possibly after v 
xxx,online). If MASTCON is defined in the IODF as a NIP console and it is 
active at IPL, it will get all NIP messages and all messages after NIP.

>Will both receive all messages and can either one respond to system action 
>messages?
If consolxx has the appropriate statements (here are mine from our sandplex):
CONSOLE DEVNUM(SYSCONS) INTIDS(Y) LEVEL(ALL) UNKNIDS(Y)
ROUTCODE(1-10,12-128)  
CONSOLE DEVNUM(HMCS) NAME(HMCS) AUTH(MASTER) MSCOPE(*)
INTIDS(Y) LEVEL(ALL) UNKNIDS(Y) ROUTCODE(1-10,12-128)  
PFKTAB(PFKTAB1)
then all messages except routcode 11 will appear on these two consoles. RC11 
has been excluded because it is a performance hog and z/OS health checker will 
nag you to remove it from being displayed.

If your MASTCON has a similar console statement with DEVNUM(ucb) then it is not 
the HMCS that I talked about earlier. Same things apply for the routing codes.

Action messages appear coloured on both the HMCS and a regular MCS console 
depending on their descriptor code (unless there are MPF exits that change the 
DC and possibly the routcode). They are shown on the SYSCON only if it had been 
explicitly activated before the message was issued.
Wait state messages (synchronous destination WTO) definitely appear on the 
SYSCON regardless of its activity state - *if* the MCS console (the one with a 
device number in consolxx) is not active. I believe synchdest messages are 
shown on the first active MCS console z/OS can find. At least that was the case 
until console restructure (and we have run without true MCS consoles for a long 
time now, so I don't have operative experience anymore). When we still had 
active MCS consoles, I seem to remember that they had to be defined a certain 
way because I still saw the wait state messages on the SYSCON - the blinking 
icon 'operating system messages' on the HMC  was my point in time when I could 
re-IPL the system.  

Hope this excurse clears things up a bit. If I got anything wrong, I'm sure Jim 
Mulder or Peter Fatzinger will chime in.

Barbara

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


Re: Virtual SHARE Ageenda

2020-06-29 Thread Seymour J Metz
Re FBA, they did it for other systems, and TSS/360 used page formatted volumes 
for everything except compatibility volumes, so from a technical perspective 
it's a no brainer, although direct use of SCSI DASD might make more sense these 
days. Politically, it's a thorny issue. I'd love to see them extend VSAM to the 
level of TSS while they're at it, e.g., VIPAM.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Clark Morris [cfmt...@uniserve.com]
Sent: Monday, June 29, 2020 6:21 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Virtual SHARE Ageenda

The virtual SHARE in August will cost only 199 USD for members, 399
USD for non-members.  There will obviously be no travel expenses if
you have access to high enough speed Internet.  There are
opportunities for Birds Of a Feather sessions.  If I sign up, I might
try to set up a BOF session on COBOL 2014, some of the very useful
features and whether they are 20 - 40 years too late because
organizations have already implemented work-arounds and won't revisit
the code?  I also am interested in discussing whether making the
effort to have z/OS handle FBA devices for FBA data sets (all VSAM,
PDSEs, page data sets, etc.) would be worthwhile and creating FBA
equivalents of SYS1.NUCLEUS (combine it with the IPL text?) SPOOL
etc.?

The schedule which gives the dates and shows the slots for BOF
sessions.
https://secure-web.cisco.com/1_VVSokqKhjADtATSHjIF0AiTdUg5Coqks2d8rrBHHXEM1FoFSi3SvmzAGRJS1YacF4kNQHbaEQxK_hOdJHR6IpklCG9geNTbPgiKBshbhsW5q0bhOGwAC4xZerhJHcU5DvKNF6wBFpV1PiKX0qesFvtzYDcKh9X7Fm-oibWsVtsVhUqt0tTEriuViat58X_qolfV5PCpO7t23kv6Ny_wadktYh8G30qHCUq61Rcv46WEcvTAhT98R35Lvagq4_jiRl10yG96zPqc58jWk8WmdMccuCqUX7vtrqTTUZqxcy8J85GbZClukrzgHLhw8Kc2-addUDxVF7DzxcDrCMitC0LNwrQumsyC_3DUT4yzxP9P-Q5SwFaePhzpyo_MoAVSFpKh7RMyNplSn_YiuhoL1Pfs3MvKUgxc0P9lPhAc6DAyY6ulfAVsJz2VH6V61Ucn/https%3A%2F%2Fevent.share.org%2Fschedule

The actual session agenda which even adjusts the times to your time
zone (mine is Atlantic Daylight Time).  If I was still a working
systems programmer, I would definitely sign up.
https://secure-web.cisco.com/1-z8rl6UqNmiXQ8TXyCJiMeNJNWLMA9IFUOODWqSx8hHtwsD0JjRDsxzmrYZWNiN92Hjy4osW5EcIq8-ejuaWpg6gC3kmSpomhjswDUFB4K2ueVuxYDbcJF01hFiJ64ARC6nmgA8jJmsceKEL61f05Gp3obQ7D7OfEg1gbm5LKb6EAU7L_AOMYIAcFC02HLhmgps3ALSeJDUbySuYjVcbgM-NtUqAPmxQGPIXm72vENxrB_x5W9dYej7capQOMdjtWussUSn-5CnRQPeX_s5WY5IJobdwe8WOL8OS0_rBSpxyIfsa7loKUWmzVix9mnGB1wdSIMpZEwT0a5AeXy_cFrtXLjHi3Cx1vJEPZptVMzF21Vzdo5j9t1CTEl2PHA9Fb_y6BYMuU86nFsnZl2QVu4-VdS8Kcvqm2xqn4WUnppKfAb3c2Mq_DT88t36KuQ90FzeE3xhea6DTvdL8jdF4_Q/https%3A%2F%2Fvirtual.share.org%2Fagenda#/?limit=20=item,oLShgQgAGAsAB9xbo,oLShgQgAGAsAB9xbo,405,120=120[0]=startsAt[0]=1

Clark Morris

--
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: Virtual SHARE Ageenda

2020-06-29 Thread Gibney, Dave
At $199, I signed up using personal money. At that price, and even if I can 
only join a subset, it's a no-brainer opportunity.

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


Re: Virtual SHARE Ageenda

2020-06-29 Thread Clark Morris
[Default] On 29 Jun 2020 18:05:01 -0700, in bit.listserv.ibm-main
sme...@gmu.edu (Seymour J Metz) wrote:

>Re FBA, they did it for other systems, and TSS/360 used page formatted volumes 
>for everything except compatibility volumes, so from a technical perspective 
>it's a no brainer, although direct use of SCSI DASD might make more sense 
>these days. Politically, it's a thorny issue. I'd love to see them extend VSAM 
>to the level of TSS while they're at it, e.g., VIPAM.

What is the logical difference between VPAM (found it in a TSS360
description) and PDSE except PDSE is an add-on (my opinion of the
decision maker who decreed that PDSE or at least a read-only subset
didn't need to be available for SYS1.PARMLIB, SYS1.NUCLEUS and
SYS1.LPALIB is complete contempt)?

Clark Morris 

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


Re: SuperWylbur Users

2020-06-29 Thread Seymour J Metz
Have you contacted SSI? What was the last release it worked on? Did you 
assemble with the new macro libraries? What are the symptoms?


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Longnecker, Dennis [dennis.longnec...@courts.wa.gov]
Sent: Monday, June 29, 2020 7:16 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: SuperWylbur Users

Hello -
Anyone here still using SuperWylbur and have it up and running on a z/OS 2.4 
system?   Bringing up 2.4 now and the JES parts aren't working correctly.  
Before I start digging into the code, I wanted to see if anyone else has solved 
it.

Thanks,
Dennis

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


Virtual SHARE Ageenda

2020-06-29 Thread Clark Morris
The virtual SHARE in August will cost only 199 USD for members, 399
USD for non-members.  There will obviously be no travel expenses if
you have access to high enough speed Internet.  There are
opportunities for Birds Of a Feather sessions.  If I sign up, I might
try to set up a BOF session on COBOL 2014, some of the very useful
features and whether they are 20 - 40 years too late because
organizations have already implemented work-arounds and won't revisit
the code?  I also am interested in discussing whether making the
effort to have z/OS handle FBA devices for FBA data sets (all VSAM,
PDSEs, page data sets, etc.) would be worthwhile and creating FBA
equivalents of SYS1.NUCLEUS (combine it with the IPL text?) SPOOL
etc.? 

The schedule which gives the dates and shows the slots for BOF
sessions.
https://event.share.org/schedule

The actual session agenda which even adjusts the times to your time
zone (mine is Atlantic Daylight Time).  If I was still a working
systems programmer, I would definitely sign up.
https://virtual.share.org/agenda#/?limit=20=item,oLShgQgAGAsAB9xbo,oLShgQgAGAsAB9xbo,405,120=120[0]=startsAt[0]=1

Clark Morris

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


SuperWylbur Users

2020-06-29 Thread Longnecker, Dennis
Hello -
Anyone here still using SuperWylbur and have it up and running on a z/OS 2.4 
system?   Bringing up 2.4 now and the JES parts aren't working correctly.  
Before I start digging into the code, I wanted to see if anyone else has solved 
it.

Thanks,
Dennis

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


Re: FW: GRSRNL Example

2020-06-29 Thread Norman Hollander
Thanks Tom.
There are some (old) memory fragments telling me that.
There are a lot of defaults, and a lot of quirks.  IIRC, if you change the name 
of DAE (such as DAESHR, which btw, can only be a max of 28 character), you 
should not include the new name.
There used to be a list of the "quirks" someplace.  Not sure if there was a 
Redbook or a WSC whitepaper/flash.  Like I said, I haven't touched this in 
(dare I say?) decades...  Think the last time I looked at this was when Nicole 
Fagan was GRS
support at IBM.  Hope you're doing well Tom!
zN

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of Tom 
Conley
Sent: Monday, June 29, 2020 1:05 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: FW: GRSRNL Example

On 6/29/2020 2:47 PM, Norman Hollander wrote:
> Perfect!  Thanks...  Don't have ACF2, but I can figure out the RACF ones.
> 
> 

Norman,

Don't put RACF in your exclusion list, it isn't necessary.

Regards,
Tom Conley

--
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: DASD migration

2020-06-29 Thread R.S.

This is good thing to start, but it is part of the story.
It covers new datasets and ...do nothing for existing ones.
For batch datasets you should also copy them to move them to new volumes.
Things get more complex for database files, however those datasets can 
be moved without and outage (vast majority of them) using database 
facilities.
There are also JES SPOOL, PAGE and other systtem datasets, I mention big 
ones. There are also some way to manage it. '


HTH

--
Radoslaw Skorupka
Lodz, Poland







W dniu 26.06.2020 o 21:52, Matthew Stitt pisze:

My favorite method of migrating to new DASD works for almost all the datasets.  Define 
the new Disk volumes to your DFSMS Storage Group configuration(s).  Change the old Disk 
volumes in each Storage Group to "DISNEW".  This method ensures that as each 
dataset is moved/copied/reorg/created it will show up on the new DASD.  Seamless and 
painless.  Finally a short outage to move the ones which are proving difficult.

Matthew

On Fri, 26 Jun 2020 09:27:42 -0600, Grant Taylor  
wrote:


On 6/26/20 9:09 AM, Bill Bishop (TMNA) wrote:

One issue that you may encounter with going to a new storage system on
a z9 processor is the speed of the ficon cards and whether the new unit
can z9 cards.  I am not sure the new Hitachi's can work with 4GB ficon.

I would naively assume that the FICON switch (director?) would
facilitate speed conversion.  Is that an incorrect assumption?






==

Jeśli nie jesteś adresatem tej wiadomości:

- powiadom nas o tym w mailu zwrotnym (dziękujemy!),
- usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś 
na dysku).
Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać 
tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) 
tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać 
karze.

mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 
Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. 
Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, 
NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 
01.01.2020 r. wynosi 169.401.468 złotych.

If you are not the addressee of this message:

- let us know by replying to this e-mail (thank you!),
- delete this message permanently (including all the copies which you have 
printed out or saved).
This message may contain legally protected information, which may be used 
exclusively by the addressee.Please be reminded that anyone who disseminates 
(copies, distributes) this message or takes any similar action, violates the 
law and may be penalised.

mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 
Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital 
City of Warsaw, 12th Commercial Division of the National Court Register, KRS 
025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 
169.401.468 as at 1 January 2020.

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


Re: AT-TLS ?

2020-06-29 Thread Lionel B Dyck
Thank you everyone for your advice - this morning will be time deep in the
doc.


Lionel B. Dyck <
Website: https://www.lbdsoftware.com

"Worry more about your character than your reputation.  Character is what
you are, reputation merely what others think you are." - John Wooden

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of
Mike Hochee
Sent: Sunday, June 28, 2020 7:08 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: AT-TLS ?

Hi Lionel, 

I did this a few years back and utilized it for a product. Below are a few
items from the product doc and a few more that remain in accessible memory
areas...

- Read the relevant sections of Comm Server IP Configuration Ref,
specifically in the chapter on Policy Agent (PA) and Policy Applications.
Also in the IP Configuration Guide, there is a chapter on AT-TLS Security
Data Protection, topic TCPIP Stack Initialization. 

- Use z/OSMF for generation of your initial set of PA config files and
inputs, then consider manually tailoring. I opted for this approach under
z/OS 2.2, but z/OSMF has undoubtedly improved greatly since then, so maybe
you can use z/OSMF exclusively w/out too much pain these days. 

- Configure the syslog daemon, and test it to ensure messages are being
collected for whatever you're interested in (TCPIP is not a pre-req for
syslogd) 

- Configure PROFILE.TCPIP, you will need to add a TTLS parm to the TCPCONFIG
statement

- Create the resource profile used to block access to the TCPIP stack during
initialization, the name of the resource will be
EZB.INITSTACK.%sysname.%tcpprocname  (it may be differently named w/ACF2 or
TSS) 

- Create a server keyring and x509 certificate, and then connect the cert to
the keyring, and depending on what you're doing you may need to permit
access so the keyring and cert can be listed (resources are
IRR.DIGTCERT.LISTRING and IRR.DIGTCERT.LIST) 

- Once you have done the above and are ready to test: 
Ensure syslogd running
Stop the TCPIP AS (there are undoubtedly less invasive ways) Start the TCPIP
AS and watch for msg EZZ4248E, after which you should start your PA daemon
(eventually, you'll want to automate this), the start will probably look
something like... /usr/lpp/tcpip/sbin/pagent -l /tmp/pagent.log -c
/etc/pagent.conf & 

- Once started, check out the following for messages... 
MVS system log
Pagent log file
Output from the pasearch -t command 

If you need additional detail, please feel free to email me directly. 

HTH,
Mike  
 

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Lionel B Dyck
Sent: Sunday, June 28, 2020 6:26 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: AT-TLS ?

Caution! This message was sent from outside your organization.

Anyone have any pointers for configuring AT-TLS on z/OS?





Lionel B. Dyck <
Website:   https://www.lbdsoftware.com

"Worry more about your character than your reputation.  Character is what
you are, reputation merely what others think you are." - John Wooden




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

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


Re: AT-TLS ?

2020-06-29 Thread Steve Beaver
Well that does take digital certs and pagant. Now there are currently no 
vendors that support AT-ALS if you are looking for something like TPX or CL/SS 
the answer is no

Sent from my iPhone

I promise you I can’t type or
Spell on any smartphone 

> On Jun 28, 2020, at 22:04, Gibney, Dave  wrote:
> 
> The details in the documentation is a bit scattered. Including separate 
> sections for  FTPS and tn3270
> 
>> -Original Message-
>> From: IBM Mainframe Discussion List  On
>> Behalf Of Lionel B Dyck
>> Sent: Sunday, June 28, 2020 3:26 PM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: AT-TLS ?
>> 
>> Anyone have any pointers for configuring AT-TLS on z/OS?
>> 
>> 
>> 
>> 
>> 
>> Lionel B. Dyck <
>> Website:
>> > 0HMszNaDT!-1owYLYM_4h_52OGm8xJE1YxqR9-
>> 4UjK4oOFwgRifVu2w8bc_kEvwxGw_GLBCA$ >
>> https://urldefense.com/v3/__https://www.lbdsoftware.com__;!!JmPEgBY0
>> HMszNaDT!-1owYLYM_4h_52OGm8xJE1YxqR9-
>> 4UjK4oOFwgRifVu2w8bc_kEvwxGw_GLBCA$
>> 
>> "Worry more about your character than your reputation.  Character is what
>> you are, reputation merely what others think you are." - John Wooden
>> 
>> 
>> 
>> 
>> --
>> 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

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


Re: AT-TLS ?

2020-06-29 Thread Wendell Lovewell
Lionel, what type of endpoints are you wanting to use AT-TLS to secure?  I 
might have some notes that would help.  

Here is some general information about diagnosing AT-TLS errors:

If there is a problem making the connection, AT-TLS will display error on the 
console.  Here are a few examples.  The endpoints were a started task (XYZSTC) 
and a CICS region (CICSA):

EZD1287I TTLS Error RC:  417 Initial Handshake 560
  LOCAL: 10.1.1.1..1213
  REMOTE: 10.1.1.1..5401
  JOBNAME: XYZSTC RULE: XYZ_STC_Rule
  USERID: STCOPER GRPID: 000F ENVID: 0013 CONNID: 06DE
EZD1287I TTLS Error RC:  435 Initial Handshake 561
  LOCAL: 10.1.1.1..5401
  REMOTE: 10.1.1.1..1213
  JOBNAME: CICSA RULE: XYZ_CICS_Rule
  USERID: CICSA GRPID: 000E ENVID: 0014 CONNID: 06DF

EZD1287I TTLS Error RC:  508 Initial Handshake 462
  LOCAL: 10.1.1.1..1206
  REMOTE: 10.1.1.1..5401
  JOBNAME: XYZSTC RULE: XYZ_STC_Rule
  USERID: STCOPER GRPID: 000F ENVID: 0010 CONNID: 06B9
EZD1287I TTLS Error RC:  438 Initial Handshake 463
  LOCAL: 10.1.1.1..5401
  REMOTE: 10.1.1.1..1206
  JOBNAME: CICSA RULE: XYZ_CICS_Rule
  USERID: CICSA GRPID: 000E ENVID: 0011 CONNID: 06BA

EZD1287I TTLS Error RC: 5006 Initial Handshake 476
  LOCAL: 10.1.1.1..5401
  REMOTE: 10.1.1.1..1173
  JOBNAME: CICSA RULE: XYZ_CICS_Rule
  USERID: CICSA GRPID: 000E ENVID: 000E CONNID: 05A4
EZD1287I TTLS Error RC:  406 Initial Handshake 477
  LOCAL: 10.1.1.1..1173
  REMOTE: 10.1.1.1..5401
  JOBNAME: XYZSTC RULE: XYZ_STC_Rule


The RC values are most helpful.  Since there is a policy used for both inbound 
(XYZ_CICS_Rule) and outbound (XYZ_STC_Rule—note the rules in play are also 
displayed on the console), there will likely be two EZD1287I messages displayed 
if there is a problem.  (Both sides will experience a problem.)  You can find 
an explanation for these in the SC14-7495-30 Cryptographic Services System 
Secure Sockets Layer Programming manual, currently in chapter 13.

SC27-3651-30 IP Configuration Reference contains the syntax for the AT-TLS 
policy (/etc/pagent_TTLS.conf).

GC27-3652-30 IP Diagnosis Guide may be useful if you are getting GSK errors.

SA23-2292-30 Security Server RACF Command Language Reference contains the 
syntax for the RACDCERT instructions.

If you need to see the GKY messages, set the Trace value in the TTLSGroupAction 
parms for both the XYZ_CICS_Rule and XYZ_STC_Rule to Trace 255.  When you 
upload /etc/pagent_TTLS.conf, the policy agent will re-install the policy.

If you make RACF changes to the keyrings, you need to tell the policy agent to 
refresh it’s settings for them.  You can do this by changing the 
EnvironmentAction value & reloading the pagent_TTLS.conf file.

Hth,
Wendell

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


Re: AT-TLS ?

2020-06-29 Thread Lionel B Dyck
The goal is to enable RRSF which requires AT-TLS and then enable secure FTP TLS 
 and TN3270 with it.  Installing CoZ:SFTP for improved sftp capabilities as 
well.

Thanks

Lionel B. Dyck <
Website: https://www.lbdsoftware.com

"Worry more about your character than your reputation.  Character is what you 
are, reputation merely what others think you are." - John Wooden

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Wendell Lovewell
Sent: Monday, June 29, 2020 8:38 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: AT-TLS ?

Lionel, what type of endpoints are you wanting to use AT-TLS to secure?  I 
might have some notes that would help.  

Here is some general information about diagnosing AT-TLS errors:

If there is a problem making the connection, AT-TLS will display error on the 
console.  Here are a few examples.  The endpoints were a started task (XYZSTC) 
and a CICS region (CICSA):

EZD1287I TTLS Error RC:  417 Initial Handshake 560
  LOCAL: 10.1.1.1..1213
  REMOTE: 10.1.1.1..5401
  JOBNAME: XYZSTC RULE: XYZ_STC_Rule
  USERID: STCOPER GRPID: 000F ENVID: 0013 CONNID: 06DE EZD1287I 
TTLS Error RC:  435 Initial Handshake 561
  LOCAL: 10.1.1.1..5401
  REMOTE: 10.1.1.1..1213
  JOBNAME: CICSA RULE: XYZ_CICS_Rule
  USERID: CICSA GRPID: 000E ENVID: 0014 CONNID: 06DF

EZD1287I TTLS Error RC:  508 Initial Handshake 462
  LOCAL: 10.1.1.1..1206
  REMOTE: 10.1.1.1..5401
  JOBNAME: XYZSTC RULE: XYZ_STC_Rule
  USERID: STCOPER GRPID: 000F ENVID: 0010 CONNID: 06B9 EZD1287I 
TTLS Error RC:  438 Initial Handshake 463
  LOCAL: 10.1.1.1..5401
  REMOTE: 10.1.1.1..1206
  JOBNAME: CICSA RULE: XYZ_CICS_Rule
  USERID: CICSA GRPID: 000E ENVID: 0011 CONNID: 06BA

EZD1287I TTLS Error RC: 5006 Initial Handshake 476
  LOCAL: 10.1.1.1..5401
  REMOTE: 10.1.1.1..1173
  JOBNAME: CICSA RULE: XYZ_CICS_Rule
  USERID: CICSA GRPID: 000E ENVID: 000E CONNID: 05A4 EZD1287I TTLS 
Error RC:  406 Initial Handshake 477
  LOCAL: 10.1.1.1..1173
  REMOTE: 10.1.1.1..5401
  JOBNAME: XYZSTC RULE: XYZ_STC_Rule


The RC values are most helpful.  Since there is a policy used for both inbound 
(XYZ_CICS_Rule) and outbound (XYZ_STC_Rule—note the rules in play are also 
displayed on the console), there will likely be two EZD1287I messages displayed 
if there is a problem.  (Both sides will experience a problem.)  You can find 
an explanation for these in the SC14-7495-30 Cryptographic Services System 
Secure Sockets Layer Programming manual, currently in chapter 13.

SC27-3651-30 IP Configuration Reference contains the syntax for the AT-TLS 
policy (/etc/pagent_TTLS.conf).

GC27-3652-30 IP Diagnosis Guide may be useful if you are getting GSK errors.

SA23-2292-30 Security Server RACF Command Language Reference contains the 
syntax for the RACDCERT instructions.

If you need to see the GKY messages, set the Trace value in the TTLSGroupAction 
parms for both the XYZ_CICS_Rule and XYZ_STC_Rule to Trace 255.  When you 
upload /etc/pagent_TTLS.conf, the policy agent will re-install the policy.

If you make RACF changes to the keyrings, you need to tell the policy agent to 
refresh it’s settings for them.  You can do this by changing the 
EnvironmentAction value & reloading the pagent_TTLS.conf file.

Hth,
Wendell

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


Make Your Mainframe A Digital Business Resource

2020-06-29 Thread Rob Schramm
https://www.forbes.com/sites/peterburris/2020/06/28/make-your-mainframe-a-digital-business-resource/

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


Re: MVS master consoles

2020-06-29 Thread R.S.
Every console can receive a message. Every console may be used to REPLY, 
however SYSCON is handicapped - it cannot be used for RACF-related tasks 
since it does not support LOGON.
Any other console like OSA-ICC or legacy 3270 box attached to 3174 
channel attached, or VTAM console, or SYSG console (from HMC) - all of 
them do support RACF LOGON.


--
Radoslaw Skorupka
Lodz, Poland






W dniu 29.06.2020 o 19:13, Alan Altmark pisze:

Hi.  I'm learning some things about MVS consoles.I have both the PD
console (SYSCON - aka Operating System Messages task on the HMC) and a
local 3270 console (named MVSMAST) active.  Both have all routing codes
assigned.  This is in a virtual machine, so SYSCON works with the #CP
VINPUT VMSG command and displays line mode output.

Will both receive all messages and can either one respond to system action
messages?

What I really don't want is for use of the 3270 console to interfere with
what's going on with SYSCON.   Someone DIALs into the 3270 console and all
of sudden the PD console stops getting messages or some such.  As you can
tell, there's a lot about MVS console management I don't grok.  I've
looked in the books, of course, but all that did was confuse me a bit
more.  It assumed I already understood various aspects of how consoles
work.

I know I can vary MVSMAST inactive at system startup and require them to
activate it manually via #CP VINPUT VMSG, but that seems like mean thing
to do if I can be assured that it's presence won't materially affect
messages appearing on the PD console and it's ability to respond to any
action messages it sees.  (Yup, might be a race between human and machine,
but I expect the machine to win that race.)

Thanks.,
Alan
Alan Altmark
Senior Managing z/VM and Linux Consultant
IBM Systems Lab Services
Phone: 607-429-3323 | Mobile: 607-321-7556
E-mail: altma...@us.ibm.com
   Endicott, NY  USA


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





==

Jeśli nie jesteś adresatem tej wiadomości:

- powiadom nas o tym w mailu zwrotnym (dziękujemy!),
- usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś 
na dysku).
Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać 
tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) 
tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać 
karze.

mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 
Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. 
Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, 
NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 
01.01.2020 r. wynosi 169.401.468 złotych.

If you are not the addressee of this message:

- let us know by replying to this e-mail (thank you!),
- delete this message permanently (including all the copies which you have 
printed out or saved).
This message may contain legally protected information, which may be used 
exclusively by the addressee.Please be reminded that anyone who disseminates 
(copies, distributes) this message or takes any similar action, violates the 
law and may be penalised.

mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 
Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital 
City of Warsaw, 12th Commercial Division of the National Court Register, KRS 
025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 
169.401.468 as at 1 January 2020.

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


Re: AT-TLS ?

2020-06-29 Thread Roberto Halais
GSK trace was very helpful!

On Mon, Jun 29, 2020 at 6:14 AM Lionel B Dyck  wrote:

> Thank you everyone for your advice - this morning will be time deep in the
> doc.
>
>
> Lionel B. Dyck <
> Website: https://www.lbdsoftware.com
>
> "Worry more about your character than your reputation.  Character is what
> you are, reputation merely what others think you are." - John Wooden
>
> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf
> Of
> Mike Hochee
> Sent: Sunday, June 28, 2020 7:08 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: AT-TLS ?
>
> Hi Lionel,
>
> I did this a few years back and utilized it for a product. Below are a few
> items from the product doc and a few more that remain in accessible memory
> areas...
>
> - Read the relevant sections of Comm Server IP Configuration Ref,
> specifically in the chapter on Policy Agent (PA) and Policy Applications.
> Also in the IP Configuration Guide, there is a chapter on AT-TLS Security
> Data Protection, topic TCPIP Stack Initialization.
>
> - Use z/OSMF for generation of your initial set of PA config files and
> inputs, then consider manually tailoring. I opted for this approach under
> z/OS 2.2, but z/OSMF has undoubtedly improved greatly since then, so maybe
> you can use z/OSMF exclusively w/out too much pain these days.
>
> - Configure the syslog daemon, and test it to ensure messages are being
> collected for whatever you're interested in (TCPIP is not a pre-req for
> syslogd)
>
> - Configure PROFILE.TCPIP, you will need to add a TTLS parm to the
> TCPCONFIG
> statement
>
> - Create the resource profile used to block access to the TCPIP stack
> during
> initialization, the name of the resource will be
> EZB.INITSTACK.%sysname.%tcpprocname  (it may be differently named w/ACF2 or
> TSS)
>
> - Create a server keyring and x509 certificate, and then connect the cert
> to
> the keyring, and depending on what you're doing you may need to permit
> access so the keyring and cert can be listed (resources are
> IRR.DIGTCERT.LISTRING and IRR.DIGTCERT.LIST)
>
> - Once you have done the above and are ready to test:
> Ensure syslogd running
> Stop the TCPIP AS (there are undoubtedly less invasive ways) Start the
> TCPIP
> AS and watch for msg EZZ4248E, after which you should start your PA daemon
> (eventually, you'll want to automate this), the start will probably look
> something like... /usr/lpp/tcpip/sbin/pagent -l /tmp/pagent.log -c
> /etc/pagent.conf &
>
> - Once started, check out the following for messages...
> MVS system log
> Pagent log file
> Output from the pasearch -t command
>
> If you need additional detail, please feel free to email me directly.
>
> HTH,
> Mike
>
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Lionel B Dyck
> Sent: Sunday, June 28, 2020 6:26 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: AT-TLS ?
>
> Caution! This message was sent from outside your organization.
>
> Anyone have any pointers for configuring AT-TLS on z/OS?
>
>
>
>
>
> Lionel B. Dyck <
> Website:   https://www.lbdsoftware.com
>
> "Worry more about your character than your reputation.  Character is what
> you are, reputation merely what others think you are." - John Wooden
>
>
>
>
> --
> 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
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
-- 
Politics: Poli (many) - tics (blood sucking parasites)

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


MVS master consoles

2020-06-29 Thread Alan Altmark
Hi.  I'm learning some things about MVS consoles.I have both the PD 
console (SYSCON - aka Operating System Messages task on the HMC) and a 
local 3270 console (named MVSMAST) active.  Both have all routing codes 
assigned.  This is in a virtual machine, so SYSCON works with the #CP 
VINPUT VMSG command and displays line mode output.

Will both receive all messages and can either one respond to system action 
messages?

What I really don't want is for use of the 3270 console to interfere with 
what's going on with SYSCON.   Someone DIALs into the 3270 console and all 
of sudden the PD console stops getting messages or some such.  As you can 
tell, there's a lot about MVS console management I don't grok.  I've 
looked in the books, of course, but all that did was confuse me a bit 
more.  It assumed I already understood various aspects of how consoles 
work.

I know I can vary MVSMAST inactive at system startup and require them to 
activate it manually via #CP VINPUT VMSG, but that seems like mean thing 
to do if I can be assured that it's presence won't materially affect 
messages appearing on the PD console and it's ability to respond to any 
action messages it sees.  (Yup, might be a race between human and machine, 
but I expect the machine to win that race.)

Thanks.,
Alan 
Alan Altmark
Senior Managing z/VM and Linux Consultant
IBM Systems Lab Services
Phone: 607-429-3323 | Mobile: 607-321-7556
E-mail: altma...@us.ibm.com 
  Endicott, NY  USA


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


Re: MVS master consoles

2020-06-29 Thread Seymour J Metz
Somewhat oversimplified, a console receives anything with matching routing 
codes and can do anything permitted by its authority. The authority is 
controlled by the console definition and by security profiles in, e.g., RACF.

The issue that may affect you is the VM environment. What happens to the 
virtual HMC messages if the operator is diconnected? What happens to the 3270 
output if nobody is dialed in? What happens if someone does a #CP DISC instead 
of a #CP RESET on the virtual 3270?

See z/OS Version 2 Release 4 MVS Planning: Operations, SA23-1390-40.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Alan Altmark [alan_altm...@us.ibm.com]
Sent: Monday, June 29, 2020 1:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: MVS master consoles

Hi.  I'm learning some things about MVS consoles.I have both the PD
console (SYSCON - aka Operating System Messages task on the HMC) and a
local 3270 console (named MVSMAST) active.  Both have all routing codes
assigned.  This is in a virtual machine, so SYSCON works with the #CP
VINPUT VMSG command and displays line mode output.

Will both receive all messages and can either one respond to system action
messages?

What I really don't want is for use of the 3270 console to interfere with
what's going on with SYSCON.   Someone DIALs into the 3270 console and all
of sudden the PD console stops getting messages or some such.  As you can
tell, there's a lot about MVS console management I don't grok.  I've
looked in the books, of course, but all that did was confuse me a bit
more.  It assumed I already understood various aspects of how consoles
work.

I know I can vary MVSMAST inactive at system startup and require them to
activate it manually via #CP VINPUT VMSG, but that seems like mean thing
to do if I can be assured that it's presence won't materially affect
messages appearing on the PD console and it's ability to respond to any
action messages it sees.  (Yup, might be a race between human and machine,
but I expect the machine to win that race.)

Thanks.,
Alan
Alan Altmark
Senior Managing z/VM and Linux Consultant
IBM Systems Lab Services
Phone: 607-429-3323 | Mobile: 607-321-7556
E-mail: altma...@us.ibm.com
  Endicott, NY  USA


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


GRSRNL Example

2020-06-29 Thread Norman Hollander
Been a while since I've done this.  Anyone have a good example
of a GRSRNL for a Sysplex?  DASD only shared among the Sysplex
members.
TIA!
zN

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


Re: GRSRNL Example

2020-06-29 Thread Edgington, Jerry
Here is what I have.
// 
/*  SYSTEMS EXCLUSION RESOURCE NAME LIST*/ 
// 
/*  */ 
RNLDEF RNL(EXCL) TYPE(SPECIFIC)
   QNAME(SYSDSN)   
   RNAME(SYS1.DCMLIB)  
RNLDEF RNL(EXCL) TYPE(GENERIC) 
   QNAME(SYSDSN)   
   RNAME(SYS1.DUMP)
// 
/*  SYSTEMS EXCLUSION RESOURCE NAME LIST - PATTERN  */ 
// 
/*  */ 
RNLDEF RNL(EXCL) TYPE(SPECIFIC)
   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP1)
RNLDEF RNL(EXCL) TYPE(SPECIFIC)
   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP2)  
RNLDEF RNL(EXCL) TYPE(SPECIFIC)  
   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP3)  
RNLDEF RNL(EXCL) TYPE(SPECIFIC)  
   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP4)  
//   
/*  SYSTEMS CONVERSION NAME LIST - RNLDEF STATEMENTS*/   
//   
RNLDEF RNL(CON) TYPE(PATTERN)
   QNAME(*)   /* CONVERT ALL RESERVES   */   
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(IGDCDSXS)/* SMS RESOURCE NAME  */   
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SPZAPLIB)/* ISPF AND LINKEAGE EDITOR   */   
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSIEWLP)/* ISPF AND LINKEAGE EDITOR   */   
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSIGGV2)/* CATALOGS   */   
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSZRACF)/* RACF DATABASE  */   
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSZVVDS)/* VVDS   */   
RNLDEF RNL(CON) TYPE(GENERIC)   
   QNAME(SYSVTOC) /* DISK VTOC  */
//
/*  SYSTEMS INCLUSION RESOURCE NAME LIST*/
//
/*  */
RNLDEF RNL(INCL) TYPE(GENERIC)
   QNAME(SYSDSN) RNAME(IXGLOGR)   
RNLDEF RNL(INCL) TYPE(GENERIC)
   QNAME(SYSDSN)  
RNLDEF RNL(INCL) TYPE(GENERIC)
   QNAME(SYSIKJBC)
RNLDEF RNL(INCL) TYPE(GENERIC)
   QNAME(SYSZVOLS) /* AUTO TAPE SWITCHING AND VOLUMES   */
/*  */
//
/*  CA ACF2 */
//
RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN)  RNAME(ACF.ACF2.LOGONIDS)   
RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN)  RNAME(ACF.ACF2.ALTLIDS)
RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN)  RNAME(ACF.ACF2.RULES)  
RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN)  RNAME(ACF.ACF2.ALTRULES)   
RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN)  RNAME(ACF.ACF2.INFOSTG)
RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN)  RNAME(ACF.ACF2.ALTINFO)  
   
RNLDEF RNL(EXCL) TYPE(GENERIC)  QNAME(SYSVSAM) RNAME(ACF.ACF2)  
RNLDEF RNL(EXCL) TYPE(GENERIC)  QNAME(SYSDSN)  RNAME(ACF.ACF2)  
/*  

Re: GRSRNL Example

2020-06-29 Thread PINION, RICHARD W.
This is what we are using.

/*  SYSTEMS EXCLUSION RESOURCE NAME LIST - RNLDEF STATEMENTS*/ 
  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  - 1 Line(s) not Displayed 
RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(SYS1.DEVB.DAE) 
RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(SYS1.FXPA.DAE) 
RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(SYS1.PRDA.DAE) 
RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(SYS1.BRODCAST) 
  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  - 7 Line(s) not Displayed 
/*  SYSTEM INCLUSION RESOURCE NAME LIST - RNLDEF STATEMENTS */ 
  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  - 2 Line(s) not Displayed 
RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SYSDSN)   
RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SPFEDIT)  
RNLDEF RNL(INCL) TYPE(GENERIC) QNAME(SYSZVOLS) 
  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  - 3 Line(s) not Displayed 
/*  SYSTEM INCLUSION RESOURCE NAME LIST - RNLDEF STATEMENTS */ 
  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  - 3 Line(s) not Displayed 
/*  RESERVE CONVERSION RESOURCE NAME LIST - RNLDEF STATEMENTS   */ 
  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  - 2 Line(s) not Displayed 
RNLDEF RNL(CON) TYPE(PATTERN)  QNAME(*)
  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  - 5 Line(s) not Displayed

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Norman Hollander
Sent: Monday, June 29, 2020 1:54 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: GRSRNL Example

[External Email. Exercise caution when clicking links or opening attachments.]

Been a while since I've done this.  Anyone have a good example of a GRSRNL for 
a Sysplex?  DASD only shared among the Sysplex members.
TIA!
zN

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Confidentiality notice: 
This e-mail message, including any attachments, may contain legally privileged 
and/or confidential information. If you are not the intended recipient(s), or 
the employee or agent responsible for delivery of this message to the intended 
recipient(s), you are hereby notified that any dissemination, distribution, or 
copying of this e-mail message is strictly prohibited. If you have received 
this message in error, please immediately notify the sender and delete this 
e-mail message from your computer.

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


Re: GRSRNL Example

2020-06-29 Thread Jesse 1 Robinson
The two examples given--from Richard Pinion and Jerry Edington--differ quite 
significantly aside from entries for optional products that a shop may or may 
not run. Our list, which has evolved over many decades, resembles Jerry's much 
more than Richard's. I'm not aware of any problems here, but I have to question 
whether all entries are necessary/useful. This an arena where entries get added 
but seldom removed. 

Is there a consensus for spare vs. verbose?

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Norman Hollander
Sent: Monday, June 29, 2020 11:47 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):FW: GRSRNL Example

CAUTION EXTERNAL EMAIL

Perfect!  Thanks...  Don't have ACF2, but I can figure out the RACF ones.


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Edgington, Jerry
Sent: Monday, June 29, 2020 11:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: GRSRNL Example

Here is what I have.
//

/*  SYSTEMS EXCLUSION RESOURCE NAME LIST*/

//

/*  */

RNLDEF RNL(EXCL) TYPE(SPECIFIC)

   QNAME(SYSDSN)

   RNAME(SYS1.DCMLIB)

RNLDEF RNL(EXCL) TYPE(GENERIC)

   QNAME(SYSDSN)

   RNAME(SYS1.DUMP)

//

/*  SYSTEMS EXCLUSION RESOURCE NAME LIST - PATTERN  */

//

/*  */

RNLDEF RNL(EXCL) TYPE(SPECIFIC)

   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP1)

RNLDEF RNL(EXCL) TYPE(SPECIFIC)

   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP2)
RNLDEF RNL(EXCL) TYPE(SPECIFIC)
   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP3)
RNLDEF RNL(EXCL) TYPE(SPECIFIC)
   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP4)
//
/*  SYSTEMS CONVERSION NAME LIST - RNLDEF STATEMENTS*/
//
RNLDEF RNL(CON) TYPE(PATTERN)
   QNAME(*)   /* CONVERT ALL RESERVES   */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(IGDCDSXS)/* SMS RESOURCE NAME  */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SPZAPLIB)/* ISPF AND LINKEAGE EDITOR   */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSIEWLP)/* ISPF AND LINKEAGE EDITOR   */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSIGGV2)/* CATALOGS   */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSZRACF)/* RACF DATABASE  */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSZVVDS)/* VVDS   */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSVTOC) /* DISK VTOC  */
//
/*  SYSTEMS INCLUSION RESOURCE NAME LIST*/
//
/*  */
RNLDEF RNL(INCL) TYPE(GENERIC)
   QNAME(SYSDSN) RNAME(IXGLOGR)
RNLDEF RNL(INCL) TYPE(GENERIC)
   QNAME(SYSDSN)
RNLDEF RNL(INCL) TYPE(GENERIC)
   QNAME(SYSIKJBC)
RNLDEF RNL(INCL) TYPE(GENERIC)
   QNAME(SYSZVOLS) /* AUTO TAPE SWITCHING AND VOLUMES   */
/*  */
//
/*  CA ACF2 */
//
RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN)  RNAME(ACF.ACF2.LOGONIDS) RNLDEF 
RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN)  RNAME(ACF.ACF2.ALTLIDS) RNLDEF 
RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN)  RNAME(ACF.ACF2.RULES) RNLDEF RNL(EXCL) 
TYPE(SPECIFIC) QNAME(SYSDSN)  RNAME(ACF.ACF2.ALTRULES) RNLDEF RNL(EXCL) 
TYPE(SPECIFIC) QNAME(SYSDSN)  RNAME(ACF.ACF2.INFOSTG) RNLDEF RNL(EXCL) 
TYPE(SPECIFIC) QNAME(SYSDSN)  RNAME(ACF.ACF2.ALTINFO)

RNLDEF RNL(EXCL) TYPE(GENERIC)  QNAME(SYSVSAM) RNAME(ACF.ACF2) RNLDEF RNL(EXCL) 
TYPE(GENERIC)  QNAME(SYSDSN)  RNAME(ACF.ACF2)
/*  */

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Norman Hollander
Sent: Monday, June 29, 2020 1:54 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: GRSRNL Example

Been a while since I've done this.  Anyone have a good example of a GRSRNL for 
a Sysplex?  DASD only shared among the Sysplex members.
TIA!
zN



Re: FW: GRSRNL Example

2020-06-29 Thread Tom Conley

On 6/29/2020 2:47 PM, Norman Hollander wrote:

Perfect!  Thanks...  Don't have ACF2, but I can figure out the RACF ones.




Norman,

Don't put RACF in your exclusion list, it isn't necessary.

Regards,
Tom Conley

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


Re: GRSRNL Example [EXTERNAL]

2020-06-29 Thread Norman Hollander
You are correct Paul.  If one member of the Sysplex has a different GRSRNL than 
the other(s),
you will get the 064 wait state.  Whenever I change PARMLIB members, I create a 
new IEASYS
which includes any new members.  That way, if you have a brain fart along the 
way, you can
easily backout.  I'd have to check if the SETGRSRNL command replaces the entire 
list, or appends
the new list.  GRSRNL can have multiple members.  So if you want IBM's (00) and 
yours appended,
you could easily do that.  
zN


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Feller, Paul
Sent: Monday, June 29, 2020 12:57 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: GRSRNL Example [EXTERNAL]

We don't update our GRSRNL to much.  Last time it was update was in 2016.  
There is one thing you might want to watch.  We ran into an issue one time when 
changes did get made an lpar got IPL before a SET GRSRNL=xx command was issues. 
 The lpar would not IPL, it went into a wait state.  I don't recall how we got 
out of the situation.  We may have backed out the changes and then IPLed.  
After that we may have put the changes back in and did the SET GRSRNL=xx 
command.  It has been a few years.

So now we have a warning at the top of the member indicating this issue could 
happen if the SET GRSRNL=xx command does not get done before an IPL is done.



Thanks..

Paul Feller
GTS Mainframe Technical Support

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Jesse 1 Robinson
Sent: Monday, June 29, 2020 2:20 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: GRSRNL Example [EXTERNAL]

The two examples given--from Richard Pinion and Jerry Edington--differ quite 
significantly aside from entries for optional products that a shop may or may 
not run. Our list, which has evolved over many decades, resembles Jerry's much 
more than Richard's. I'm not aware of any problems here, but I have to question 
whether all entries are necessary/useful. This an arena where entries get added 
but seldom removed. 

Is there a consensus for spare vs. verbose?

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Norman Hollander
Sent: Monday, June 29, 2020 11:47 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):FW: GRSRNL Example

CAUTION EXTERNAL EMAIL

Perfect!  Thanks...  Don't have ACF2, but I can figure out the RACF ones.


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Edgington, Jerry
Sent: Monday, June 29, 2020 11:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: GRSRNL Example

Here is what I have.
//

/*  SYSTEMS EXCLUSION RESOURCE NAME LIST*/

//

/*  */

RNLDEF RNL(EXCL) TYPE(SPECIFIC)

   QNAME(SYSDSN)

   RNAME(SYS1.DCMLIB)

RNLDEF RNL(EXCL) TYPE(GENERIC)

   QNAME(SYSDSN)

   RNAME(SYS1.DUMP)

//

/*  SYSTEMS EXCLUSION RESOURCE NAME LIST - PATTERN  */

//

/*  */

RNLDEF RNL(EXCL) TYPE(SPECIFIC)

   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP1)

RNLDEF RNL(EXCL) TYPE(SPECIFIC)

   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP2)
RNLDEF RNL(EXCL) TYPE(SPECIFIC)
   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP3)
RNLDEF RNL(EXCL) TYPE(SPECIFIC)
   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP4)
//
/*  SYSTEMS CONVERSION NAME LIST - RNLDEF STATEMENTS*/
//
RNLDEF RNL(CON) TYPE(PATTERN)
   QNAME(*)   /* CONVERT ALL RESERVES   */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(IGDCDSXS)/* SMS RESOURCE NAME  */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SPZAPLIB)/* ISPF AND LINKEAGE EDITOR   */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSIEWLP)/* ISPF AND LINKEAGE EDITOR   */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSIGGV2)/* CATALOGS   */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSZRACF)/* RACF DATABASE  */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSZVVDS)/* VVDS   */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSVTOC) /* DISK VTOC  */
//
/*  SYSTEMS INCLUSION RESOURCE NAME LIST*/

FW: GRSRNL Example

2020-06-29 Thread Norman Hollander
Perfect!  Thanks...  Don't have ACF2, but I can figure out the RACF ones.


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of
Edgington, Jerry
Sent: Monday, June 29, 2020 11:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: GRSRNL Example

Here is what I have.
//

/*  SYSTEMS EXCLUSION RESOURCE NAME LIST*/

//

/*  */

RNLDEF RNL(EXCL) TYPE(SPECIFIC)

   QNAME(SYSDSN)

   RNAME(SYS1.DCMLIB)

RNLDEF RNL(EXCL) TYPE(GENERIC)

   QNAME(SYSDSN)

   RNAME(SYS1.DUMP)

//

/*  SYSTEMS EXCLUSION RESOURCE NAME LIST - PATTERN  */

//

/*  */

RNLDEF RNL(EXCL) TYPE(SPECIFIC)

   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP1)

RNLDEF RNL(EXCL) TYPE(SPECIFIC)

   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP2)  
RNLDEF RNL(EXCL) TYPE(SPECIFIC)  
   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP3)  
RNLDEF RNL(EXCL) TYPE(SPECIFIC)  
   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP4)  
//   
/*  SYSTEMS CONVERSION NAME LIST - RNLDEF STATEMENTS*/   
//   
RNLDEF RNL(CON) TYPE(PATTERN)
   QNAME(*)   /* CONVERT ALL RESERVES   */   
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(IGDCDSXS)/* SMS RESOURCE NAME  */   
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SPZAPLIB)/* ISPF AND LINKEAGE EDITOR   */   
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSIEWLP)/* ISPF AND LINKEAGE EDITOR   */   
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSIGGV2)/* CATALOGS   */   
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSZRACF)/* RACF DATABASE  */   
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSZVVDS)/* VVDS   */   
RNLDEF RNL(CON) TYPE(GENERIC)   
   QNAME(SYSVTOC) /* DISK VTOC  */
//
/*  SYSTEMS INCLUSION RESOURCE NAME LIST*/
//
/*  */
RNLDEF RNL(INCL) TYPE(GENERIC)
   QNAME(SYSDSN) RNAME(IXGLOGR)   
RNLDEF RNL(INCL) TYPE(GENERIC)
   QNAME(SYSDSN)  
RNLDEF RNL(INCL) TYPE(GENERIC)
   QNAME(SYSIKJBC)
RNLDEF RNL(INCL) TYPE(GENERIC)
   QNAME(SYSZVOLS) /* AUTO TAPE SWITCHING AND VOLUMES   */
/*  */
//
/*  CA ACF2 */
//
RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN)  RNAME(ACF.ACF2.LOGONIDS)   
RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN)  RNAME(ACF.ACF2.ALTLIDS)
RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN)  RNAME(ACF.ACF2.RULES)  
RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN)  RNAME(ACF.ACF2.ALTRULES)   
RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN)  RNAME(ACF.ACF2.INFOSTG)
RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN)  RNAME(ACF.ACF2.ALTINFO)

RNLDEF RNL(EXCL) TYPE(GENERIC)  QNAME(SYSVSAM) RNAME(ACF.ACF2)  
RNLDEF RNL(EXCL) TYPE(GENERIC)  QNAME(SYSDSN)  RNAME(ACF.ACF2)  
/*  */  

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of
Norman Hollander
Sent: Monday, June 29, 2020 1:54 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: GRSRNL Example

This message was sent from an external source outside of Western &
Southern's 

Re: GRSRNL Example [EXTERNAL]

2020-06-29 Thread Feller, Paul
We don't update our GRSRNL to much.  Last time it was update was in 2016.  
There is one thing you might want to watch.  We ran into an issue one time when 
changes did get made an lpar got IPL before a SET GRSRNL=xx command was issues. 
 The lpar would not IPL, it went into a wait state.  I don't recall how we got 
out of the situation.  We may have backed out the changes and then IPLed.  
After that we may have put the changes back in and did the SET GRSRNL=xx 
command.  It has been a few years.

So now we have a warning at the top of the member indicating this issue could 
happen if the SET GRSRNL=xx command does not get done before an IPL is done.



Thanks..

Paul Feller
GTS Mainframe Technical Support

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Jesse 1 Robinson
Sent: Monday, June 29, 2020 2:20 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: GRSRNL Example [EXTERNAL]

The two examples given--from Richard Pinion and Jerry Edington--differ quite 
significantly aside from entries for optional products that a shop may or may 
not run. Our list, which has evolved over many decades, resembles Jerry's much 
more than Richard's. I'm not aware of any problems here, but I have to question 
whether all entries are necessary/useful. This an arena where entries get added 
but seldom removed. 

Is there a consensus for spare vs. verbose?

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Norman Hollander
Sent: Monday, June 29, 2020 11:47 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):FW: GRSRNL Example

CAUTION EXTERNAL EMAIL

Perfect!  Thanks...  Don't have ACF2, but I can figure out the RACF ones.


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Edgington, Jerry
Sent: Monday, June 29, 2020 11:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: GRSRNL Example

Here is what I have.
//

/*  SYSTEMS EXCLUSION RESOURCE NAME LIST*/

//

/*  */

RNLDEF RNL(EXCL) TYPE(SPECIFIC)

   QNAME(SYSDSN)

   RNAME(SYS1.DCMLIB)

RNLDEF RNL(EXCL) TYPE(GENERIC)

   QNAME(SYSDSN)

   RNAME(SYS1.DUMP)

//

/*  SYSTEMS EXCLUSION RESOURCE NAME LIST - PATTERN  */

//

/*  */

RNLDEF RNL(EXCL) TYPE(SPECIFIC)

   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP1)

RNLDEF RNL(EXCL) TYPE(SPECIFIC)

   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP2)
RNLDEF RNL(EXCL) TYPE(SPECIFIC)
   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP3)
RNLDEF RNL(EXCL) TYPE(SPECIFIC)
   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP4)
//
/*  SYSTEMS CONVERSION NAME LIST - RNLDEF STATEMENTS*/
//
RNLDEF RNL(CON) TYPE(PATTERN)
   QNAME(*)   /* CONVERT ALL RESERVES   */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(IGDCDSXS)/* SMS RESOURCE NAME  */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SPZAPLIB)/* ISPF AND LINKEAGE EDITOR   */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSIEWLP)/* ISPF AND LINKEAGE EDITOR   */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSIGGV2)/* CATALOGS   */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSZRACF)/* RACF DATABASE  */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSZVVDS)/* VVDS   */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSVTOC) /* DISK VTOC  */
//
/*  SYSTEMS INCLUSION RESOURCE NAME LIST*/
//
/*  */
RNLDEF RNL(INCL) TYPE(GENERIC)
   QNAME(SYSDSN) RNAME(IXGLOGR)
RNLDEF RNL(INCL) TYPE(GENERIC)
   QNAME(SYSDSN)
RNLDEF RNL(INCL) TYPE(GENERIC)
   QNAME(SYSIKJBC)
RNLDEF RNL(INCL) TYPE(GENERIC)
   QNAME(SYSZVOLS) /* AUTO TAPE SWITCHING AND VOLUMES   */
/*  */
//
/*  CA ACF2 */
//
RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN)  

Re: GRSRNL Example [EXTERNAL]

2020-06-29 Thread Edgington, Jerry
Paul,

That can happen, if the GRSRNL is out sync between LPARs.  You would need to 
setup the LPAR with GRSRNL that is currently running on the LPAR which is still 
up.  Then after the LPAR is up and running, you might be able to issue SET 
GRSRNL=xx, depending upon the changes.  I have hit that situation before. :) 

Jerry 

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Feller, Paul
Sent: Monday, June 29, 2020 3:57 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: GRSRNL Example [EXTERNAL]

This message was sent from an external source outside of Western & Southern's 
network. Do not click links or open attachments unless you recognize the sender 
and know the contents are safe.


We don't update our GRSRNL to much.  Last time it was update was in 2016.  
There is one thing you might want to watch.  We ran into an issue one time when 
changes did get made an lpar got IPL before a SET GRSRNL=xx command was issues. 
 The lpar would not IPL, it went into a wait state.  I don't recall how we got 
out of the situation.  We may have backed out the changes and then IPLed.  
After that we may have put the changes back in and did the SET GRSRNL=xx 
command.  It has been a few years.

So now we have a warning at the top of the member indicating this issue could 
happen if the SET GRSRNL=xx command does not get done before an IPL is done.



Thanks..

Paul Feller
GTS Mainframe Technical Support

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Jesse 1 Robinson
Sent: Monday, June 29, 2020 2:20 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: GRSRNL Example [EXTERNAL]

The two examples given--from Richard Pinion and Jerry Edington--differ quite 
significantly aside from entries for optional products that a shop may or may 
not run. Our list, which has evolved over many decades, resembles Jerry's much 
more than Richard's. I'm not aware of any problems here, but I have to question 
whether all entries are necessary/useful. This an arena where entries get added 
but seldom removed. 

Is there a consensus for spare vs. verbose?

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Norman Hollander
Sent: Monday, June 29, 2020 11:47 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):FW: GRSRNL Example

CAUTION EXTERNAL EMAIL

Perfect!  Thanks...  Don't have ACF2, but I can figure out the RACF ones.


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Edgington, Jerry
Sent: Monday, June 29, 2020 11:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: GRSRNL Example

Here is what I have.
//

/*  SYSTEMS EXCLUSION RESOURCE NAME LIST*/

//

/*  */

RNLDEF RNL(EXCL) TYPE(SPECIFIC)

   QNAME(SYSDSN)

   RNAME(SYS1.DCMLIB)

RNLDEF RNL(EXCL) TYPE(GENERIC)

   QNAME(SYSDSN)

   RNAME(SYS1.DUMP)

//

/*  SYSTEMS EXCLUSION RESOURCE NAME LIST - PATTERN  */

//

/*  */

RNLDEF RNL(EXCL) TYPE(SPECIFIC)

   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP1)

RNLDEF RNL(EXCL) TYPE(SPECIFIC)

   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP2)
RNLDEF RNL(EXCL) TYPE(SPECIFIC)
   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP3)
RNLDEF RNL(EXCL) TYPE(SPECIFIC)
   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP4)
//
/*  SYSTEMS CONVERSION NAME LIST - RNLDEF STATEMENTS*/
//
RNLDEF RNL(CON) TYPE(PATTERN)
   QNAME(*)   /* CONVERT ALL RESERVES   */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(IGDCDSXS)/* SMS RESOURCE NAME  */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SPZAPLIB)/* ISPF AND LINKEAGE EDITOR   */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSIEWLP)/* ISPF AND LINKEAGE EDITOR   */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSIGGV2)/* CATALOGS   */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSZRACF)/* RACF DATABASE  */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSZVVDS)/* VVDS   */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSVTOC) /* DISK VTOC  */

Re: GRSRNL Example

2020-06-29 Thread Norman Hollander
Seems to me that too many extraneous entries could take extra processing to
scan the entries each time, and would take up extra storage.  I think moving to
more generic (or pattern) type of entries may have an advantage.  Definitely 
need
the reserves converted.  Be sure you are only sharing DASD within the Sysplex.
Outside needs special handling (and you would not be able to use Star mode).
There is a lot more reporting (D GRS commands), and GRS monitoring that would
help determine how effective the list is.
zN

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Jesse 1 Robinson
Sent: Monday, June 29, 2020 12:20 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: GRSRNL Example

The two examples given--from Richard Pinion and Jerry Edington--differ quite 
significantly aside from entries for optional products that a shop may or may 
not run. Our list, which has evolved over many decades, resembles Jerry's much 
more than Richard's. I'm not aware of any problems here, but I have to question 
whether all entries are necessary/useful. This an arena where entries get added 
but seldom removed. 

Is there a consensus for spare vs. verbose?

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Norman Hollander
Sent: Monday, June 29, 2020 11:47 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):FW: GRSRNL Example

CAUTION EXTERNAL EMAIL

Perfect!  Thanks...  Don't have ACF2, but I can figure out the RACF ones.


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Edgington, Jerry
Sent: Monday, June 29, 2020 11:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: GRSRNL Example

Here is what I have.
//

/*  SYSTEMS EXCLUSION RESOURCE NAME LIST*/

//

/*  */

RNLDEF RNL(EXCL) TYPE(SPECIFIC)

   QNAME(SYSDSN)

   RNAME(SYS1.DCMLIB)

RNLDEF RNL(EXCL) TYPE(GENERIC)

   QNAME(SYSDSN)

   RNAME(SYS1.DUMP)

//

/*  SYSTEMS EXCLUSION RESOURCE NAME LIST - PATTERN  */

//

/*  */

RNLDEF RNL(EXCL) TYPE(SPECIFIC)

   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP1)

RNLDEF RNL(EXCL) TYPE(SPECIFIC)

   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP2)
RNLDEF RNL(EXCL) TYPE(SPECIFIC)
   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP3)
RNLDEF RNL(EXCL) TYPE(SPECIFIC)
   QNAME(SYSZJES2) RNAME(SYS1.HASPCKP4)
//
/*  SYSTEMS CONVERSION NAME LIST - RNLDEF STATEMENTS*/
//
RNLDEF RNL(CON) TYPE(PATTERN)
   QNAME(*)   /* CONVERT ALL RESERVES   */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(IGDCDSXS)/* SMS RESOURCE NAME  */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SPZAPLIB)/* ISPF AND LINKEAGE EDITOR   */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSIEWLP)/* ISPF AND LINKEAGE EDITOR   */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSIGGV2)/* CATALOGS   */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSZRACF)/* RACF DATABASE  */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSZVVDS)/* VVDS   */
RNLDEF RNL(CON) TYPE(GENERIC)
   QNAME(SYSVTOC) /* DISK VTOC  */
//
/*  SYSTEMS INCLUSION RESOURCE NAME LIST*/
//
/*  */
RNLDEF RNL(INCL) TYPE(GENERIC)
   QNAME(SYSDSN) RNAME(IXGLOGR)
RNLDEF RNL(INCL) TYPE(GENERIC)
   QNAME(SYSDSN)
RNLDEF RNL(INCL) TYPE(GENERIC)
   QNAME(SYSIKJBC)
RNLDEF RNL(INCL) TYPE(GENERIC)
   QNAME(SYSZVOLS) /* AUTO TAPE SWITCHING AND VOLUMES   */
/*  */
//
/*  CA ACF2 */
//
RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN)  RNAME(ACF.ACF2.LOGONIDS) RNLDEF 
RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN)  RNAME(ACF.ACF2.ALTLIDS) RNLDEF 
RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN)  RNAME(ACF.ACF2.RULES) RNLDEF RNL(EXCL) 
TYPE(SPECIFIC) QNAME(SYSDSN)