Re: Comments in SYS1.PARMLIB

[Edward Gould]

Cheryl:


> On Aug 23, 2016, at 2:51 PM, Cheryl Watson  wrote:
> 
> Hi Ed,
> 
> Regarding "Letting IBM off with variations is nonsense.", I choose to think 
> of it as being pragmatic.  I can complain all day about how IBM's reduction 
> of staff is hurting the mainframe, but the fact is that they are doing it 
> despite anything I might say or do.  Believe me that putting people to work 
> on implementing "/" and "*/" in each parmlib member is NOT going to make it 
> into the line items for a new release with higher priority work and reduced 
> staff size.  

I believe in holding IBM to a standard that they themselves developed. I 
shudder to think that each parmlib member will have it own syntax. This goes 
agains every thing that IBM espouses. I will be long gone and I still think 
that this will be a dangerous precedent. As I said in my previous email, I have 
had to do updates to parmlib on the fly as a fellow sysprog forgot a comma and 
all of a sudden VTAM would not come up nor CICS due to an APF issue because of 
a stupid missing comma.  Luckily I never made the mistake.  
> 
> Before I wrote up the requirements, I did a thorough study of the Parmlib 
> members and found that about half allow '*' in the first position.  Because 
> different departments work on each Parmlib member, I had to write up a 
> separate requirement for each one, and it would have taken years (if ever) to 
> get them all changed.  Then Peter Relson, who wears many hats and is trusted 
> by everyone in IBM, offered to do all the coding if he could implement the 
> '*' version because, obviously, it's the least amount of coding (if a = '*' 
> then bypass).  I said that it would meet my requirements, the MVSE 
> Requirements committee agreed, and he had it done a week later.  If we had 
> forced IBM to do it the "right way", it wouldn't be done today.  At least now 
> there is an option to put comments in the Parmlib members that didn't have 
> them.
Then write a requirement that *ALL* parmlib members must use the same syntax. 
That allows IBM to come up with one standard. It shouldn't be up to the users 
to fight over syntax on each member. I have seen (and IBM agreed to) several 
global requirements (like the syntax for parmlib idea) that IBM agreed to and 
with a two GUIDE meetings it was accepted. The problem is I don’t remember 
which one it was (its been 20+ years) :(

> 
> And as my first email suggested, I think it would make a lot of sense for 
> people to add a comment box at the top of every Parmlib member that includes 
> not only an example of comments, but provides a place to put comments.  You 
> can save newbies a lot of trouble (and down time) in the future.  

Sorry I don’t buy off on that. Besides a *LOT* of people just copy what comes 
in the servpac now days. It dangerous to accept that people are going to read 
comments first. That is why IBM doc is pretty much world class (until OMVS came 
along that is)
> 
> I think this is just one of many compromises that we'll need to make with a 
> reduced IBM staff, but I'd rather work within the system and get some things 
> accomplished.  (I could only wish our political parties could do the same.)  
> ;-)

Documentation (good) is an IBM mainstay. Changing the rules for each member 
will let the CA’s of the world do their own thing and we will be left with no 
standards. 

> 
> All my best,
> Cheryl
Standardization is a good thing as it allow sysprogs to update every member the 
same way. Changing the standard (such as it is) is just asking for a 
catastrophe.


> 
> SNIP---

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

Re: SMPE SCPP Custompac trying to change from "Full replace" to "Software Upgrade".

[John Mattson]

With IBM's excellent help, found the answer in the FM.  Says right
there that software upgrade is for ZOS only, and I am only upgrading CICS.
I am new consultant into this very old shop which has ways of doing
things which predate serverpac and such. This is going to be "interesting".

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

Re: Comments in SYS1.PARMLIB

[Charles Mills]

Perfect is the enemy of good.

(Attributed to Voltaire, Confucius and others.)

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Cheryl Watson
Sent: Tuesday, August 23, 2016 3:52 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Comments in SYS1.PARMLIB

Hi Ed,

Regarding "Letting IBM off with variations is nonsense.", I choose to think of 
it as being pragmatic.  I can complain all day about how IBM's reduction of 
staff is hurting the mainframe, but the fact is that they are doing it despite 
anything I might say or do.  Believe me that putting people to work on 
implementing "/" and "*/" in each parmlib member is NOT going to make it into 
the line items for a new release with higher priority work and reduced staff 
size.  

Before I wrote up the requirements, I did a thorough study of the Parmlib 
members and found that about half allow '*' in the first position.  Because 
different departments work on each Parmlib member, I had to write up a separate 
requirement for each one, and it would have taken years (if ever) to get them 
all changed.  Then Peter Relson, who wears many hats and is trusted by everyone 
in IBM, offered to do all the coding if he could implement the '*' version 
because, obviously, it's the least amount of coding (if a = '*' then bypass).  
I said that it would meet my requirements, the MVSE Requirements committee 
agreed, and he had it done a week later.  If we had forced IBM to do it the 
"right way", it wouldn't be done today.  At least now there is an option to put 
comments in the Parmlib members that didn't have them.

And as my first email suggested, I think it would make a lot of sense for 
people to add a comment box at the top of every Parmlib member that includes 
not only an example of comments, but provides a place to put comments.  You can 
save newbies a lot of trouble (and down time) in the future.  

I think this is just one of many compromises that we'll need to make with a 
reduced IBM staff, but I'd rather work within the system and get some things 
accomplished.  (I could only wish our political parties could do the same.)  ;-)

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

Re: Comments in SYS1.PARMLIB

[Cheryl Watson]

Hi Ed,

Regarding "Letting IBM off with variations is nonsense.", I choose to think of 
it as being pragmatic.  I can complain all day about how IBM's reduction of 
staff is hurting the mainframe, but the fact is that they are doing it despite 
anything I might say or do.  Believe me that putting people to work on 
implementing "/" and "*/" in each parmlib member is NOT going to make it into 
the line items for a new release with higher priority work and reduced staff 
size.  

Before I wrote up the requirements, I did a thorough study of the Parmlib 
members and found that about half allow '*' in the first position.  Because 
different departments work on each Parmlib member, I had to write up a separate 
requirement for each one, and it would have taken years (if ever) to get them 
all changed.  Then Peter Relson, who wears many hats and is trusted by everyone 
in IBM, offered to do all the coding if he could implement the '*' version 
because, obviously, it's the least amount of coding (if a = '*' then bypass).  
I said that it would meet my requirements, the MVSE Requirements committee 
agreed, and he had it done a week later.  If we had forced IBM to do it the 
"right way", it wouldn't be done today.  At least now there is an option to put 
comments in the Parmlib members that didn't have them.

And as my first email suggested, I think it would make a lot of sense for 
people to add a comment box at the top of every Parmlib member that includes 
not only an example of comments, but provides a place to put comments.  You can 
save newbies a lot of trouble (and down time) in the future.  

I think this is just one of many compromises that we'll need to make with a 
reduced IBM staff, but I'd rather work within the system and get some things 
accomplished.  (I could only wish our political parties could do the same.)  ;-)

All my best,
Cheryl

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Edward Gould
Sent: Tuesday, August 23, 2016 3:25 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Comments in SYS1.PARMLIB

Cheryl:

Thanks for all your work on this.
However it occurs to me that IBM is still not living up to the spirit of the 
request.
I would suggest that the “/*" and the “*/”  standard (since day one mind you) 
IS the gold standard.
Letting IBM off with variations is nonsense.
The first “GROUP” who really went off the reservation (with documentation and 
other IBM standards) was the OMVS Group.
Letting IBM set this kind of “standard” is dangerous IMO. More than one time I 
have had to make on the fly updates to Parmlib so that the IPL could be 
corrected and restarted loosing 30+ minutes (assuming I was present) in one 
case two hours. Just because of a finger check. This allowing IBM to change the 
rules for each member is IMO short sighted and will land more pressure down the 
road to standardize things… Bad decision on IBM’s part in both cases, IMO.

Ed
 
> On Aug 23, 2016, at 9:02 AM, Cheryl Watson  wrote:
> 
> Hi all,
> 
> It's true that not all Parmlib members support the same format, but 
> the Init & Tuning Guide has been updated to show which type of 
> comments are allowed in each member.
> 
> In 2011, I created a dozen SHARE requirements to add comments to the 
> remaining Parmlib members that didn't support them.  Peter Relson was 
> kind enough to come to our aid and implemented comments for the then 
> active Parmlib members.  This excerpt comes from our Tuning Letter 2013 No. 3:
> ===
> Comments
> 
> Change documentation is very dear to my heart, so I have been upset 
> for years by the fact that you could not add comments to many of the 
> parmlib members. I got so frustrated that I wrote up SHARE 
> requirements for many of the members to either add or modify the ability to 
> add comments.
> 
> Thanks to z/OS guru Peter Relson of IBM, who works with the SHARE MVSE 
> requirements committee, we now have an APAR, OA38328 (z/OS 1.12-1.13, 
> 17Apr2013, New Function - Parmlib Comment Support), that address many 
> of these requirements. The following parmlib members have been 
> modified to allow an asterisk in position 1 of a line to indicate that 
> the rest of the line is a comment:
> 
> COMMNDxx - Commands to be issued at IPL GTFPARM (or the parmlib member 
> identified by the GTF procedure) - Parameters used by the Generalized 
> Trace Facility
> IEAABD00 - Specifies data to be dumped to SYSABEND
> IEACMD00 - IBM-supplied commands to be issued at IPL
> IEADMP00 - Specifies data to be dumped to SYSUDUMP
> IEADMR00 - Specifies data to be dumped to SYSMDUMP IEAPAKxx - Link 
> Pack Area (LPA) pack list IEASYSxx - System parameter list LPALSTxx - 
> Link Pack Area (LPA) library list VATLSTxx - Volume attribute list
> 
> I just LOVE this APAR! Because you might start adding comments after 
> the PTF is applied, you should probably determine a standard method of 
> 

Re: JOBDEF DUPL_JOB=NODELAY|DELAY option

[Ronald Kristel]

Yes, I Believe there is a "$TJobclass(x),dupl_job=Nodelay/Delay

Kind Regards,

Ronald Kristel

> Date: Tue, 23 Aug 2016 19:39:14 +
> From: robert.ah.pr...@gmail.com
> Subject: JOBDEF DUPL_JOB=NODELAY|DELAY option
> To: IBM-MAIN@LISTSERV.UA.EDU
> 
> Is there any way of enabling this on a per-jobclass basis?
> 
> Robert
> -- 
> Robert AH Prins
> robert.ah.pr...@gmail.com
> No programming (yet) @ 
> 
> --
> 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

JOBDEF DUPL_JOB=NODELAY|DELAY option

[Robert Prins]

Is there any way of enabling this on a per-jobclass basis?

Robert
-- 
Robert AH Prins
robert.ah.pr...@gmail.com
No programming (yet) @ 

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

Re: Comments in SYS1.PARMLIB

[Edward Gould]

Cheryl:

Thanks for all your work on this.
However it occurs to me that IBM is still not living up to the spirit of the 
request.
I would suggest that the “/*" and the “*/”  standard (since day one mind you) 
IS the gold standard.
Letting IBM off with variations is nonsense.
The first “GROUP” who really went off the reservation (with documentation and 
other IBM standards) was the OMVS Group.
Letting IBM set this kind of “standard” is dangerous IMO. More than one time I 
have had to make on the fly updates to Parmlib so that the IPL could be 
corrected and restarted loosing 30+ minutes (assuming I was present) in one 
case two hours. Just because of a finger check. This allowing IBM to change the 
rules for each member is IMO short sighted and will land more pressure down the 
road to standardize things…
Bad decision on IBM’s part in both cases, IMO.

Ed
 
> On Aug 23, 2016, at 9:02 AM, Cheryl Watson  wrote:
> 
> Hi all,
> 
> It's true that not all Parmlib members support the same format, but the Init
> & Tuning Guide has been updated to show which type of comments are allowed
> in each member.
> 
> In 2011, I created a dozen SHARE requirements to add comments to the
> remaining Parmlib members that didn't support them.  Peter Relson was kind
> enough to come to our aid and implemented comments for the then active
> Parmlib members.  This excerpt comes from our Tuning Letter 2013 No. 3:
> ===
> Comments
> 
> Change documentation is very dear to my heart, so I have been upset for
> years by the fact that you could not add comments to many of the parmlib
> members. I got so frustrated that I wrote up SHARE requirements for many of
> the members to either add or modify the ability to add comments.
> 
> Thanks to z/OS guru Peter Relson of IBM, who works with the SHARE MVSE
> requirements committee, we now have an APAR, OA38328 (z/OS 1.12-1.13,
> 17Apr2013, New Function - Parmlib Comment Support), that address many of
> these requirements. The following parmlib members have been modified to
> allow an asterisk in position 1 of a line to indicate that the rest of the
> line is a comment:
> 
> COMMNDxx - Commands to be issued at IPL
> GTFPARM (or the parmlib member identified by the GTF procedure) - Parameters
> used by the Generalized Trace Facility
> IEAABD00 - Specifies data to be dumped to SYSABEND
> IEACMD00 - IBM-supplied commands to be issued at IPL
> IEADMP00 - Specifies data to be dumped to SYSUDUMP
> IEADMR00 - Specifies data to be dumped to SYSMDUMP
> IEAPAKxx - Link Pack Area (LPA) pack list
> IEASYSxx - System parameter list
> LPALSTxx - Link Pack Area (LPA) library list
> VATLSTxx - Volume attribute list
> 
> I just LOVE this APAR! Because you might start adding comments after the PTF
> is applied, you should probably determine a standard method of documentation
> that everyone can follow. This would normally include the date and time,
> description of the change (including the reason for the change), and the
> person making the change. You should also make a note of any dependencies
> (i.e. a change in one parameter in this parmlib requires a change in another
> parameter in another parmlib). Figure 3 is an example of a "flower box" (as
> we used to call them) that we would insert at the beginning of every parmlib
> member.  (Note - in Word, but not email, the right hand asterisks are in
> line.)
> 
> Figure 3 - Documenting a Parmlib Member
> **
> * Notes:
> *
> * If you change parameter xxx, then you  *
> *   should make a corresponding change   *
> *   in member xx.*
> **
> **
> * Change Log:*
> * 2012/03/20, 10:30am - CLW - Changed    *
> *  to  to add PROGB1 suffix  *
> * 2012/03/27, 8am - CLW - Added x  per   *
> *  memo from  dated 3/25/12  *
> **
> **
> 
> Unfortunately, you can't use the same comment box in all parmlib members,
> because comments aren't always indicated in the same way. The IEASYMxx
> member only allows comments when enclosed within the bounds of a /* and an
> */; TSOKEY00 only allows comments at the end of all parameters; and members
> IGDSMSxx, IPCSPRxx, and IVTPRM00 don't allow any comments.
> 
> RECOMMENDATION: Apply the PTF and start adding comments to these
> long-neglected parmlib members.
> =
> 
> I hope this help,
> Cheryl
> 
> Cheryl Watson
> Watson & Walker, Inc.
> www.watsonwalker.com
> 
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Feller, Paul
> Sent: 

Frustrated with IBM knowledge center

[Ward, Mike S]

Hello all, I have been trying to find a z/OS knowledge Center for z/OS V2R2 
that will install on windows. So far I have found one that installs on z/OS 
using SMP. Is there one for windows and if so can I download it for 
installation?

Any help appreciated.

Thanks.

==
This email, and any files transmitted with it, is confidential and intended 
solely for the use of the individual or entity to which it is addressed. If you 
have received this email in error, please notify the system manager. This 
message contains confidential information and is intended only for the 
individual named. If you are not the named addressee, you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this message by mistake and delete 
this e-mail from your system. If you are not the intended recipient, you are 
notified that disclosing, copying, distributing or taking any action in 
reliance on the contents of this information is strictly prohibited.

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

Re: Comments in SYS1.PARMLIB

[J R]

Use the REXX approach. Start with a comment that signals that the new standard 
syntax is being used. 
/* CARDINAL SYNTAX */

Sent from my iPhone

> On Aug 23, 2016, at 12:08, Mike Schwab  wrote:
> 
> But how would you switch over to the new syntax?
> 
> On Tue, Aug 23, 2016 at 10:44 AM, Paul Gilmartin
> <000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
>> On Tue, 23 Aug 2016 10:02:30 -0400, Cheryl Watson wrote:
>>> 
>>> It's true that not all Parmlib members support the same format, but the Init
>>> & Tuning Guide has been updated to show which type of comments are allowed
>>> in each member.
>> Wouldn't that resource (and the customers') have been more productively
>> spent in making the syntax uniform?  Use Utilities commands as a model.
>> 
>> -- gil
>> 
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> 
> 
> -- 
> Mike A Schwab, Springfield IL USA

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

Re: SMPLOG usage

[Pommier, Rex]

Hi Radoslaw,

Yes, SMp/E will use SMPLOG until it is full, then switch to SMPLOGA.  Once that 
is full, it will not go back to SMPLOG.  According to the manual:

"If the SMPLOGA data set is full, the extra log data is written to the SMPOUT 
data set, with the date and time stamp encrypted"

I have secondary space defined for my SMPLOG datasets.  AFAIK, I've never had 
an issue with them.  That may be because I haven't had to use them.  :-)

I don't know of SMP/E actually using the data in the log file, I believe they 
are more for auditing and external problem resolution.

Rex

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of R.S.
Sent: Tuesday, August 23, 2016 1:08 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: SMPLOG usage

(SMP/E)
SMPLOG is being used with DISP=MOD.
That means it will grow and grow until it get full (x37 abend) and then 
alternative log dataset (SMPLOGA) is used.
Am I right with the above?

Q1. What happens when SMPLOGA is full? Is SMPLOG used again with overwrite?
Q2. Is it reasonable to provide secondary space for SMPLOG datasets? 
IMHO it shoudl work as SMF (SYS1.MANx) - only primary allocation, and "round 
robin" switchover.
Q3. Does SMP/E use the information from SMPLOG? I mean "internal" usage, not 
LIST LOG command.

--
Radoslaw Skorupka
Lodz, Poland






--
Treść tej wiadomości może zawierać informacje prawnie chronione Banku 
przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie 
jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem 
niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania 
adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne działanie o podobnym charakterze jest prawnie zabronione i może być 
karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie 
zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość 
włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is 
intended solely for business use of the addressee. This e-mail may only be 
received by the addressee and may not be disclosed to any third parties. If you 
are not the intended addressee of this e-mail or the employee authorized to 
forward it to the addressee, be advised that any dissemination, copying, 
distribution or any other similar activity is legally prohibited and may be 
punishable. If you received this e-mail by mistake please advise the sender 
immediately by using the reply facility in your e-mail software and delete 
permanently this e-mail including any copies of it either printed or saved to 
hard drive.

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, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. 
Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości 
wpłacony) wynosi 168.955.696 złotych.


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

The information contained in this message is confidential, protected from 
disclosure and may be legally privileged.  If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful.  If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format.  Thank you.

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

SMPLOG usage

[R.S.]

(SMP/E)
SMPLOG is being used with DISP=MOD.
That means it will grow and grow until it get full (x37 abend) and then 
alternative log dataset (SMPLOGA) is used.

Am I right with the above?

Q1. What happens when SMPLOGA is full? Is SMPLOG used again with overwrite?
Q2. Is it reasonable to provide secondary space for SMPLOG datasets? 
IMHO it shoudl work as SMF (SYS1.MANx) - only primary allocation, and 
"round robin" switchover.
Q3. Does SMP/E use the information from SMPLOG? I mean "internal" usage, 
not LIST LOG command.


--
Radoslaw Skorupka
Lodz, Poland






--
Treść tej wiadomości może zawierać informacje prawnie chronione Banku 
przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie 
jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem 
niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania 
adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne działanie o podobnym charakterze jest prawnie zabronione i może być 
karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie 
zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość 
włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is 
intended solely for business use of the addressee. This e-mail may only be 
received by the addressee and may not be disclosed to any third parties. If you 
are not the intended addressee of this e-mail or the employee authorized to 
forward it to the addressee, be advised that any dissemination, copying, 
distribution or any other similar activity is legally prohibited and may be 
punishable. If you received this e-mail by mistake please advise the sender 
immediately by using the reply facility in your e-mail software and delete 
permanently this e-mail including any copies of it either printed or saved to 
hard drive.

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, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. 
Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości 
wpłacony) wynosi 168.955.696 złotych.


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

Re: Comments in SYS1.PARMLIB

[Ed Jaffe]

On 8/23/2016 8:44 AM, Paul Gilmartin wrote:

Wouldn't that resource (and the customers') have been more productively
spent in making the syntax uniform?  Use Utilities commands as a model.


Not according to IBM. It was this or nothing.

--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/

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

Re: Comments in SYS1.PARMLIB

[Tom Conley]

On 8/23/2016 11:44 AM, Paul Gilmartin wrote:

On Tue, 23 Aug 2016 10:02:30 -0400, Cheryl Watson wrote:


It's true that not all Parmlib members support the same format, but the Init
& Tuning Guide has been updated to show which type of comments are allowed
in each member.


Wouldn't that resource (and the customers') have been more productively
spent in making the syntax uniform?  Use Utilities commands as a model.

-- gil

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



No, because the changes to NIP code would have been prohibitive.

Regards,
Tom Conley

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

SMPE SCPP Custompac trying to change from "Full replace" to "Software Upgrade".

[John Mattson]

At the beginning of the SCPP install dialog you get an option for "F" full
install or "S" software upgrade.  I should have chosen "S", but I mucked up
and did "F".  So I want to change to "S".  The manual says I should be able
to do
I-Install
C-Create
CReate-create again
DELETE-delete old install
and then get back to the "F" or "S" panel, but that is not happening.  It
creates a new install, but it seems that "F" is still selected.
Does anyone know how to get around this.  IFF it is just a single variable,
I should be able to change that variable... but I do not know what it is.

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

Re: Comments in SYS1.PARMLIB

[Mike Schwab]

But how would you switch over to the new syntax?

On Tue, Aug 23, 2016 at 10:44 AM, Paul Gilmartin
<000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Tue, 23 Aug 2016 10:02:30 -0400, Cheryl Watson wrote:
>>
>>It's true that not all Parmlib members support the same format, but the Init
>>& Tuning Guide has been updated to show which type of comments are allowed
>>in each member.
>>
> Wouldn't that resource (and the customers') have been more productively
> spent in making the syntax uniform?  Use Utilities commands as a model.
>
> -- gil
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

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

Re: Loading Java dump into IPCS

[Janet Graff]

Thanks Eileen!

Janet

> -X options would probably go into the the STDENV IBM_JAVA_OPTIONS parm 

>Eileen

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

Re: Comments in SYS1.PARMLIB

[Ed Jaffe]

On 8/23/2016 7:01 AM, Tom Conley wrote:


This was one of our big SHARE requirements and we worked hard at it. 
You should be able to put comments in any SYS1.PARMLIB member now.  If 
you find a member that's not supported, please let us know.


What he said!

Also, if your company is a SHARE member, please, Please, PLEASE don't 
open an RFE and then beg your "friends" through this list and other 
social media channels to click LIKE on it. [Sheesh!] It simply doesn't work.


Use the SHARE requirements system and get real results. 
http://www.share.org/page/requirements-&-advocacy


--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/

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

Re: Comments in SYS1.PARMLIB

[Jesse 1 Robinson]

One additional gotcha for IEASYMxx. Guess how I learned this. An entire sysplex 
would not IPL. From KC:

"Do not use nested comments in this parmlib member."

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


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Cheryl Watson
Sent: Tuesday, August 23, 2016 7:13 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Comments in SYS1.PARMLIB

Hi all,

Most of the problems have been in the older members, but it's been getting 
better since IBM included this section in the Init & Tuning Guide.  (ISVs 
should be aware of these guidelines too.):
==
General syntax rules for the creation of members

The following general syntax rules apply to the creation of most parmlib 
members. You can find the description of the exceptions to these rules under 
specific members. The general rules are:

-- Logical record size is 80 bytes.
-- Block size must be a multiple of 80.
-- Any columns between 1 and 71 can contain data.
-- Statements are entered in uppercase characters.
-- Suffix member identifiers can be any combination of A-Z and 0-9, though some 
member identifiers may allow other characters.
-- Columns 72 through 80 are ignored.
-- For some parmlib members, continuation is indicated by a comma followed by 
one or more blanks after the last entry on a record.
-- Leading blanks are suppressed. A record therefore need not start at a 
particular column.
-- Suffix member identifiers (such as LNK=A2) can be any alphanumeric 
combination.
-- Comments for some parmlib members are indicated by using /* and */ as the 
delimiters in columns 1-71, for example:
/*comment*/
/* and */
characters within a single-quoted string are usually not treated as comment 
delimiters. For nested comments, delimiters must be balanced. For example, you 
can nest comments as follows:
/*comment1/*comment2*/*/
Some parmlib members require other methods. Check specific parmlib members for 
information about specifying comments.



Cheers!
Cheryl

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Elardus Engelbrecht
Sent: Tuesday, August 23, 2016 9:40 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Comments in SYS1.PARMLIB

Richards, Robert B. wrote:

>This has probably been asked before, but a quick search of the archives did 
>not yield the results I was looking for.

>Do all members of SYS1.PARMLIB now support /*  */  commenting?

No. There is only one standard with this name: 'NO STANDARDS'   ;-)


IEASYSxx has this:
DIAG=00,  COMMENT

ARCCMDxx:
/* COMMENT */
SETSYS ...

ADYSETxx:

* COMMENT
  DAE ...

Oh, not all members have the same set of continuation syntax. 

Some members have this:

 STATEMENT KEYWORD,

Others like ARCCMDxx has this:

SETSYS -
  NODEBUG

I could go on...

Good luck trying to untangle this...

Groete / Greetings
Elardus Engelbrecht


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

Re: Comments in SYS1.PARMLIB

[Paul Gilmartin]

On Tue, 23 Aug 2016 10:02:30 -0400, Cheryl Watson wrote:
>
>It's true that not all Parmlib members support the same format, but the Init
>& Tuning Guide has been updated to show which type of comments are allowed
>in each member.
> 
Wouldn't that resource (and the customers') have been more productively
spent in making the syntax uniform?  Use Utilities commands as a model.

-- gil

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

Re: Backup JES2 Spool & Restore with Warmstart

[Jousma, David]

I should have added that we specify DUPLEX=on, which means all updates go to 
both.  
_
Dave Jousma
Manager Mainframe Engineering, Assistant Vice President
david.jou...@53.com
1830 East Paris, Grand Rapids, MI  49546 MD RSCB2H
p 616.653.8429
f 616.653.2717


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jousma, David
Sent: Tuesday, August 23, 2016 11:15 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Backup JES2 Spool & Restore with Warmstart

That’s what we do.  Primary in the CF, secondary on disk.   When we recover to 
our DR systems, we restart JES and it prompts us that the primary is missing, 
and do we want to start from the secondary.   Can't say we have ever noticed a 
problem.

_
Dave Jousma
Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com
1830 East Paris, Grand Rapids, MI  49546 MD RSCB2H p 616.653.8429 f 616.653.2717

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jesse 1 Robinson
Sent: Tuesday, August 23, 2016 11:05 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Backup JES2 Spool & Restore with Warmstart

A question that just occurred to me: Where does your primary checkpoint live? 
This is pretty ancient history, but in the mid-90s when we first went to 
parallel sysplex, I tried putting the primary checkpoint in the coupling 
facility. This meant that the secondary checkpoint was the only one mirrored. 
Or flashed, if we had had that technology then. The secondary is not updated as 
often as the primary. Just wondering...

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

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Mike Shorkend
Sent: Monday, August 22, 2016 10:09 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Backup JES2 Spool & Restore with Warmstart

One of my customers does a daily flash copy and then IPLs off the copy. No 
issues with JES2 warm start. They are using DS8870 and z/OS 2.2 but have been 
doing this for years without problems.

HTH

Mike


On 23 August 2016 at 04:46, Ron Hawkins  wrote:

> Ken,
>
> FlashCopy consistency group "should" give you the same P-i-T as Synch 
> and Asynch Remote Copy. Sounds like you should report a problem.
>
> Attended a few DR rehearsals where JEs2 has warm started without a hitch.
>
> Have you tried ShadowImage At-Time split (if you have HDS)?
>
> Ron
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Ken Smith
> Sent: Monday, August 22, 2016 8:16 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [IBM-MAIN] Backup JES2 Spool & Restore with Warmstart
>
> I've not had the opportunity to work with mirroring but sounds like 
> your flashcopy to secondary is the same thing I'm doing minus the 
> transmission.
> And, the purpose of a consistency group is to have a point in time 
> copy across volumes.
>
> Anyone else?  Ken
>
> On Thu, Aug 18, 2016 at 5:44 PM, Jesse 1 Robinson 
>  >
> wrote:
>
> > We've been mirroring for DR for many years. In the beginning, with 
> > late 90s technology, we could not mirror spool. Now with FICON over 
> > DWDM we mirror spool routinely. I can't remember getting any error 
> > on
> > JES2 restart after recovery, which includes flashcopy of the 
> > secondary (XRC target) copy to a tertiary copy that we IPL from.
> >
> > .
> > .
> > .
> > J.O.Skip Robinson
> > Southern California Edison Company
> > Electric Dragon Team Paddler
> > SHARE MVS Program Co-Manager
> > 323-715-0595 Mobile
> > 626-302-7535 Office
> > robin...@sce.com
> >
> >
> > -Original Message-
> > From: IBM Mainframe Discussion List 
> > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ken Smith
> > Sent: Thursday, August 18, 2016 12:55 PM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: (External):Backup JES2 Spool & Restore with Warmstart
> >
> > For those of us stuck with tape backup, physical or virtual, are you 
> > recovering JES2 and able to do a warm start?
> >
> > I made the rash assumption that Flashcopy (space efficient) with 
> > consistency group across the spool and checkpoint volumes would 
> > work, but it does not - get checkpoint errors and have to do a 
> > format and cold
> start.
> >
> > Read in JES2 manual that back up is not supported, however, not sure 
> > this was written before or after flash copy was invented.  Seems to 
> > me that at any instant in time the data should be consistent?  Also, 
> > disk mirroring should have the same problem but I doubt it does.
> >
> > Thoughts?
> >
> > Ken Smith
> > Comptroller of Maryland
--
Mike 

Re: Backup JES2 Spool & Restore with Warmstart

[Jousma, David]

That’s what we do.  Primary in the CF, secondary on disk.   When we recover to 
our DR systems, we restart JES and it prompts us that the primary is missing, 
and do we want to start from the secondary.   Can't say we have ever noticed a 
problem.

_
Dave Jousma
Manager Mainframe Engineering, Assistant Vice President
david.jou...@53.com
1830 East Paris, Grand Rapids, MI  49546 MD RSCB2H
p 616.653.8429
f 616.653.2717

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jesse 1 Robinson
Sent: Tuesday, August 23, 2016 11:05 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Backup JES2 Spool & Restore with Warmstart

A question that just occurred to me: Where does your primary checkpoint live? 
This is pretty ancient history, but in the mid-90s when we first went to 
parallel sysplex, I tried putting the primary checkpoint in the coupling 
facility. This meant that the secondary checkpoint was the only one mirrored. 
Or flashed, if we had had that technology then. The secondary is not updated as 
often as the primary. Just wondering...

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

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Mike Shorkend
Sent: Monday, August 22, 2016 10:09 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Backup JES2 Spool & Restore with Warmstart

One of my customers does a daily flash copy and then IPLs off the copy. No 
issues with JES2 warm start. They are using DS8870 and z/OS 2.2 but have been 
doing this for years without problems.

HTH

Mike


On 23 August 2016 at 04:46, Ron Hawkins  wrote:

> Ken,
>
> FlashCopy consistency group "should" give you the same P-i-T as Synch 
> and Asynch Remote Copy. Sounds like you should report a problem.
>
> Attended a few DR rehearsals where JEs2 has warm started without a hitch.
>
> Have you tried ShadowImage At-Time split (if you have HDS)?
>
> Ron
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Ken Smith
> Sent: Monday, August 22, 2016 8:16 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [IBM-MAIN] Backup JES2 Spool & Restore with Warmstart
>
> I've not had the opportunity to work with mirroring but sounds like 
> your flashcopy to secondary is the same thing I'm doing minus the 
> transmission.
> And, the purpose of a consistency group is to have a point in time 
> copy across volumes.
>
> Anyone else?  Ken
>
> On Thu, Aug 18, 2016 at 5:44 PM, Jesse 1 Robinson 
>  >
> wrote:
>
> > We've been mirroring for DR for many years. In the beginning, with 
> > late 90s technology, we could not mirror spool. Now with FICON over 
> > DWDM we mirror spool routinely. I can't remember getting any error 
> > on
> > JES2 restart after recovery, which includes flashcopy of the 
> > secondary (XRC target) copy to a tertiary copy that we IPL from.
> >
> > .
> > .
> > .
> > J.O.Skip Robinson
> > Southern California Edison Company
> > Electric Dragon Team Paddler
> > SHARE MVS Program Co-Manager
> > 323-715-0595 Mobile
> > 626-302-7535 Office
> > robin...@sce.com
> >
> >
> > -Original Message-
> > From: IBM Mainframe Discussion List 
> > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ken Smith
> > Sent: Thursday, August 18, 2016 12:55 PM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: (External):Backup JES2 Spool & Restore with Warmstart
> >
> > For those of us stuck with tape backup, physical or virtual, are you 
> > recovering JES2 and able to do a warm start?
> >
> > I made the rash assumption that Flashcopy (space efficient) with 
> > consistency group across the spool and checkpoint volumes would 
> > work, but it does not - get checkpoint errors and have to do a 
> > format and cold
> start.
> >
> > Read in JES2 manual that back up is not supported, however, not sure 
> > this was written before or after flash copy was invented.  Seems to 
> > me that at any instant in time the data should be consistent?  Also, 
> > disk mirroring should have the same problem but I doubt it does.
> >
> > Thoughts?
> >
> > Ken Smith
> > Comptroller of Maryland
--
Mike Shorkend
m...@shorkend.com
www.shorkend.com
Tel: +972524208743
Fax: +97239772196


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

This e-mail transmission contains information that is confidential and may be 
privileged.   It is intended only for the addressee(s) named above. If you 
receive this e-mail in error, please do not read, copy or disseminate it in any 
manner. If you are not the intended recipient, any 

Re: Backup JES2 Spool & Restore with Warmstart

[Feller, Paul]

The secondary should be getting updated at the same time as the primary that is 
in the coupling facility.  The secondary is your fall back if something happens 
to the structure in the CF.  We run that way and have not issues with a warm 
start at DR.  There is some complaints from JES2 about stuff that was executing 
at the time we "cut" over for a DR test.

Thanks..

Paul Feller
AGT Mainframe Technical Support


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jesse 1 Robinson
Sent: Tuesday, August 23, 2016 10:05
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Backup JES2 Spool & Restore with Warmstart

A question that just occurred to me: Where does your primary checkpoint live? 
This is pretty ancient history, but in the mid-90s when we first went to 
parallel sysplex, I tried putting the primary checkpoint in the coupling 
facility. This meant that the secondary checkpoint was the only one mirrored. 
Or flashed, if we had had that technology then. The secondary is not updated as 
often as the primary. Just wondering...

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

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Mike Shorkend
Sent: Monday, August 22, 2016 10:09 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Backup JES2 Spool & Restore with Warmstart

One of my customers does a daily flash copy and then IPLs off the copy. No 
issues with JES2 warm start. They are using DS8870 and z/OS 2.2 but have been 
doing this for years without problems.

HTH

Mike


On 23 August 2016 at 04:46, Ron Hawkins  wrote:

> Ken,
>
> FlashCopy consistency group "should" give you the same P-i-T as Synch 
> and Asynch Remote Copy. Sounds like you should report a problem.
>
> Attended a few DR rehearsals where JEs2 has warm started without a hitch.
>
> Have you tried ShadowImage At-Time split (if you have HDS)?
>
> Ron
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Ken Smith
> Sent: Monday, August 22, 2016 8:16 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [IBM-MAIN] Backup JES2 Spool & Restore with Warmstart
>
> I've not had the opportunity to work with mirroring but sounds like 
> your flashcopy to secondary is the same thing I'm doing minus the 
> transmission.
> And, the purpose of a consistency group is to have a point in time 
> copy across volumes.
>
> Anyone else?  Ken
>
> On Thu, Aug 18, 2016 at 5:44 PM, Jesse 1 Robinson 
>  >
> wrote:
>
> > We've been mirroring for DR for many years. In the beginning, with 
> > late 90s technology, we could not mirror spool. Now with FICON over 
> > DWDM we mirror spool routinely. I can't remember getting any error 
> > on
> > JES2 restart after recovery, which includes flashcopy of the 
> > secondary (XRC target) copy to a tertiary copy that we IPL from.
> >
> > .
> > .
> > .
> > J.O.Skip Robinson
> > Southern California Edison Company
> > Electric Dragon Team Paddler
> > SHARE MVS Program Co-Manager
> > 323-715-0595 Mobile
> > 626-302-7535 Office
> > robin...@sce.com
> >
> >
> > -Original Message-
> > From: IBM Mainframe Discussion List 
> > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ken Smith
> > Sent: Thursday, August 18, 2016 12:55 PM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: (External):Backup JES2 Spool & Restore with Warmstart
> >
> > For those of us stuck with tape backup, physical or virtual, are you 
> > recovering JES2 and able to do a warm start?
> >
> > I made the rash assumption that Flashcopy (space efficient) with 
> > consistency group across the spool and checkpoint volumes would 
> > work, but it does not - get checkpoint errors and have to do a 
> > format and cold
> start.
> >
> > Read in JES2 manual that back up is not supported, however, not sure 
> > this was written before or after flash copy was invented.  Seems to 
> > me that at any instant in time the data should be consistent?  Also, 
> > disk mirroring should have the same problem but I doubt it does.
> >
> > Thoughts?
> >
> > Ken Smith
> > Comptroller of Maryland
--
Mike Shorkend
m...@shorkend.com
www.shorkend.com
Tel: +972524208743
Fax: +97239772196


--
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: Backup JES2 Spool & Restore with Warmstart

[Jesse 1 Robinson]

A question that just occurred to me: Where does your primary checkpoint live? 
This is pretty ancient history, but in the mid-90s when we first went to 
parallel sysplex, I tried putting the primary checkpoint in the coupling 
facility. This meant that the secondary checkpoint was the only one mirrored. 
Or flashed, if we had had that technology then. The secondary is not updated as 
often as the primary. Just wondering...

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

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Mike Shorkend
Sent: Monday, August 22, 2016 10:09 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Backup JES2 Spool & Restore with Warmstart

One of my customers does a daily flash copy and then IPLs off the copy. No 
issues with JES2 warm start. They are using DS8870 and z/OS 2.2 but have been 
doing this for years without problems.

HTH

Mike


On 23 August 2016 at 04:46, Ron Hawkins  wrote:

> Ken,
>
> FlashCopy consistency group "should" give you the same P-i-T as Synch 
> and Asynch Remote Copy. Sounds like you should report a problem.
>
> Attended a few DR rehearsals where JEs2 has warm started without a hitch.
>
> Have you tried ShadowImage At-Time split (if you have HDS)?
>
> Ron
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Ken Smith
> Sent: Monday, August 22, 2016 8:16 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [IBM-MAIN] Backup JES2 Spool & Restore with Warmstart
>
> I've not had the opportunity to work with mirroring but sounds like 
> your flashcopy to secondary is the same thing I'm doing minus the 
> transmission.
> And, the purpose of a consistency group is to have a point in time 
> copy across volumes.
>
> Anyone else?  Ken
>
> On Thu, Aug 18, 2016 at 5:44 PM, Jesse 1 Robinson 
>  >
> wrote:
>
> > We've been mirroring for DR for many years. In the beginning, with 
> > late 90s technology, we could not mirror spool. Now with FICON over 
> > DWDM we mirror spool routinely. I can't remember getting any error 
> > on
> > JES2 restart after recovery, which includes flashcopy of the 
> > secondary (XRC target) copy to a tertiary copy that we IPL from.
> >
> > .
> > .
> > .
> > J.O.Skip Robinson
> > Southern California Edison Company
> > Electric Dragon Team Paddler
> > SHARE MVS Program Co-Manager
> > 323-715-0595 Mobile
> > 626-302-7535 Office
> > robin...@sce.com
> >
> >
> > -Original Message-
> > From: IBM Mainframe Discussion List 
> > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ken Smith
> > Sent: Thursday, August 18, 2016 12:55 PM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: (External):Backup JES2 Spool & Restore with Warmstart
> >
> > For those of us stuck with tape backup, physical or virtual, are you 
> > recovering JES2 and able to do a warm start?
> >
> > I made the rash assumption that Flashcopy (space efficient) with 
> > consistency group across the spool and checkpoint volumes would 
> > work, but it does not - get checkpoint errors and have to do a 
> > format and cold
> start.
> >
> > Read in JES2 manual that back up is not supported, however, not sure 
> > this was written before or after flash copy was invented.  Seems to 
> > me that at any instant in time the data should be consistent?  Also, 
> > disk mirroring should have the same problem but I doubt it does.
> >
> > Thoughts?
> >
> > Ken Smith
> > Comptroller of Maryland
--
Mike Shorkend
m...@shorkend.com
www.shorkend.com
Tel: +972524208743
Fax: +97239772196


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

Re: [EXTERNAL] Re: Comments in SYS1.PARMLIB

[Richards, Robert B.]

Thanks to all for your participation in this thread, but specials kudos to 
Cheryl Watson and Tom Conley for their efforts.

Bob

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Dyck, Lionel B. (TRA)
Sent: Tuesday, August 23, 2016 10:18 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] Re: Comments in SYS1.PARMLIB

THANK YOU - this is great information.

--
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 Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Cheryl Watson
Sent: Tuesday, August 23, 2016 9:13 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: Comments in SYS1.PARMLIB

Hi all,

Most of the problems have been in the older members, but it's been getting 
better since IBM included this section in the Init & Tuning Guide.  (ISVs 
should be aware of these guidelines too.):
==
General syntax rules for the creation of members

The following general syntax rules apply to the creation of most parmlib 
members. You can find the description of the exceptions to these rules under 
specific members. The general rules are:

-- Logical record size is 80 bytes.
-- Block size must be a multiple of 80.
-- Any columns between 1 and 71 can contain data.
-- Statements are entered in uppercase characters.
-- Suffix member identifiers can be any combination of A-Z and 0-9, though some 
member identifiers may allow other characters.
-- Columns 72 through 80 are ignored.
-- For some parmlib members, continuation is indicated by a comma followed by 
one or more blanks after the last entry on a record.
-- Leading blanks are suppressed. A record therefore need not start at a 
particular column.
-- Suffix member identifiers (such as LNK=A2) can be any alphanumeric 
combination.
-- Comments for some parmlib members are indicated by using /* and */ as the 
delimiters in columns 1-71, for example:
/*comment*/
/* and */
characters within a single-quoted string are usually not treated as comment 
delimiters. For nested comments, delimiters must be balanced. For example, you 
can nest comments as follows:
/*comment1/*comment2*/*/
Some parmlib members require other methods. Check specific parmlib members for 
information about specifying comments.



Cheers!
Cheryl

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Elardus Engelbrecht
Sent: Tuesday, August 23, 2016 9:40 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Comments in SYS1.PARMLIB

Richards, Robert B. wrote:

>This has probably been asked before, but a quick search of the archives did 
>not yield the results I was looking for.

>Do all members of SYS1.PARMLIB now support /*  */  commenting?

No. There is only one standard with this name: 'NO STANDARDS'   ;-)


IEASYSxx has this:
DIAG=00,  COMMENT

ARCCMDxx:
/* COMMENT */
SETSYS ...

ADYSETxx:

* COMMENT
  DAE ...

Oh, not all members have the same set of continuation syntax. 

Some members have this:

 STATEMENT KEYWORD,

Others like ARCCMDxx has this:

SETSYS -
  NODEBUG

I could go on...

Good luck trying to untangle this...

Groete / Greetings
Elardus Engelbrecht

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

(null)

--
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: [EXTERNAL] Re: Comments in SYS1.PARMLIB

[Dyck, Lionel B. (TRA)]

THANK YOU - this is great information.

--
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 Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Cheryl Watson
Sent: Tuesday, August 23, 2016 9:13 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: Comments in SYS1.PARMLIB

Hi all,

Most of the problems have been in the older members, but it's been getting 
better since IBM included this section in the Init & Tuning Guide.  (ISVs 
should be aware of these guidelines too.):
==
General syntax rules for the creation of members

The following general syntax rules apply to the creation of most parmlib 
members. You can find the description of the exceptions to these rules under 
specific members. The general rules are:

-- Logical record size is 80 bytes.
-- Block size must be a multiple of 80.
-- Any columns between 1 and 71 can contain data.
-- Statements are entered in uppercase characters.
-- Suffix member identifiers can be any combination of A-Z and 0-9, though some 
member identifiers may allow other characters.
-- Columns 72 through 80 are ignored.
-- For some parmlib members, continuation is indicated by a comma followed by 
one or more blanks after the last entry on a record.
-- Leading blanks are suppressed. A record therefore need not start at a 
particular column.
-- Suffix member identifiers (such as LNK=A2) can be any alphanumeric 
combination.
-- Comments for some parmlib members are indicated by using /* and */ as the 
delimiters in columns 1-71, for example:
/*comment*/
/* and */
characters within a single-quoted string are usually not treated as comment 
delimiters. For nested comments, delimiters must be balanced. For example, you 
can nest comments as follows:
/*comment1/*comment2*/*/
Some parmlib members require other methods. Check specific parmlib members for 
information about specifying comments.



Cheers!
Cheryl

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Elardus Engelbrecht
Sent: Tuesday, August 23, 2016 9:40 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Comments in SYS1.PARMLIB

Richards, Robert B. wrote:

>This has probably been asked before, but a quick search of the archives did 
>not yield the results I was looking for.

>Do all members of SYS1.PARMLIB now support /*  */  commenting?

No. There is only one standard with this name: 'NO STANDARDS'   ;-)


IEASYSxx has this:
DIAG=00,  COMMENT

ARCCMDxx:
/* COMMENT */
SETSYS ...

ADYSETxx:

* COMMENT
  DAE ...

Oh, not all members have the same set of continuation syntax. 

Some members have this:

 STATEMENT KEYWORD,

Others like ARCCMDxx has this:

SETSYS -
  NODEBUG

I could go on...

Good luck trying to untangle this...

Groete / Greetings
Elardus Engelbrecht

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

(null)

--
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: Comments in SYS1.PARMLIB

[Cheryl Watson]

Hi all,

Most of the problems have been in the older members, but it's been getting 
better since IBM included this section in the Init & Tuning Guide.  (ISVs 
should be aware of these guidelines too.):
==
General syntax rules for the creation of members

The following general syntax rules apply to the creation of most parmlib 
members. You can find the description of the exceptions to these rules under 
specific
members. The general rules are:

-- Logical record size is 80 bytes.
-- Block size must be a multiple of 80.
-- Any columns between 1 and 71 can contain data.
-- Statements are entered in uppercase characters.
-- Suffix member identifiers can be any combination of A-Z and 0-9, though some 
member identifiers may allow other characters.
-- Columns 72 through 80 are ignored.
-- For some parmlib members, continuation is indicated by a comma followed by 
one or more blanks after the last entry on a record.
-- Leading blanks are suppressed. A record therefore need not start at a 
particular column.
-- Suffix member identifiers (such as LNK=A2) can be any alphanumeric 
combination.
-- Comments for some parmlib members are indicated by using /* and */ as the 
delimiters in columns 1-71, for example:
/*comment*/ 
/* and */ 
characters within a single-quoted string are usually not treated as comment 
delimiters. For nested comments, delimiters must be balanced. For example, you 
can nest comments as follows:
/*comment1/*comment2*/*/
Some parmlib members require other methods. Check specific parmlib members for 
information about specifying comments.



Cheers!
Cheryl

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Elardus Engelbrecht
Sent: Tuesday, August 23, 2016 9:40 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Comments in SYS1.PARMLIB

Richards, Robert B. wrote:

>This has probably been asked before, but a quick search of the archives did 
>not yield the results I was looking for.

>Do all members of SYS1.PARMLIB now support /*  */  commenting?

No. There is only one standard with this name: 'NO STANDARDS'   ;-)


IEASYSxx has this:
DIAG=00,  COMMENT

ARCCMDxx:
/* COMMENT */
SETSYS ...

ADYSETxx:

* COMMENT
  DAE ...

Oh, not all members have the same set of continuation syntax. 

Some members have this:

 STATEMENT KEYWORD,

Others like ARCCMDxx has this:

SETSYS -
  NODEBUG

I could go on...

Good luck trying to untangle this...

Groete / Greetings
Elardus Engelbrecht

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

(null)

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

Re: Comments in SYS1.PARMLIB

[Elardus Engelbrecht]

Cheryl Watson wrote:

>I just LOVE this APAR! 

No comments... ;-)

Sorry, Cheryl, but I really *love* your post. Please continue with your nice 
posts.

Groete / Greetings
Elardus Engelbrecht

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

Re: Comments in SYS1.PARMLIB

[Cheryl Watson]

Hi all,

It's true that not all Parmlib members support the same format, but the Init
& Tuning Guide has been updated to show which type of comments are allowed
in each member.

In 2011, I created a dozen SHARE requirements to add comments to the
remaining Parmlib members that didn't support them.  Peter Relson was kind
enough to come to our aid and implemented comments for the then active
Parmlib members.  This excerpt comes from our Tuning Letter 2013 No. 3:
===
Comments

Change documentation is very dear to my heart, so I have been upset for
years by the fact that you could not add comments to many of the parmlib
members. I got so frustrated that I wrote up SHARE requirements for many of
the members to either add or modify the ability to add comments.

Thanks to z/OS guru Peter Relson of IBM, who works with the SHARE MVSE
requirements committee, we now have an APAR, OA38328 (z/OS 1.12-1.13,
17Apr2013, New Function - Parmlib Comment Support), that address many of
these requirements. The following parmlib members have been modified to
allow an asterisk in position 1 of a line to indicate that the rest of the
line is a comment:

COMMNDxx - Commands to be issued at IPL
GTFPARM (or the parmlib member identified by the GTF procedure) - Parameters
used by the Generalized Trace Facility
IEAABD00 - Specifies data to be dumped to SYSABEND
IEACMD00 - IBM-supplied commands to be issued at IPL
IEADMP00 - Specifies data to be dumped to SYSUDUMP
IEADMR00 - Specifies data to be dumped to SYSMDUMP
IEAPAKxx - Link Pack Area (LPA) pack list
IEASYSxx - System parameter list
LPALSTxx - Link Pack Area (LPA) library list
VATLSTxx - Volume attribute list

I just LOVE this APAR! Because you might start adding comments after the PTF
is applied, you should probably determine a standard method of documentation
that everyone can follow. This would normally include the date and time,
description of the change (including the reason for the change), and the
person making the change. You should also make a note of any dependencies
(i.e. a change in one parameter in this parmlib requires a change in another
parameter in another parmlib). Figure 3 is an example of a "flower box" (as
we used to call them) that we would insert at the beginning of every parmlib
member.  (Note - in Word, but not email, the right hand asterisks are in
line.)

Figure 3 - Documenting a Parmlib Member
**
* Notes:
*
* If you change parameter xxx, then you  *
*   should make a corresponding change   *
*   in member xx.*
**
**
* Change Log:*
* 2012/03/20, 10:30am - CLW - Changed    *
*  to  to add PROGB1 suffix  *
* 2012/03/27, 8am - CLW - Added x  per   *
*  memo from  dated 3/25/12  *
**
**

Unfortunately, you can't use the same comment box in all parmlib members,
because comments aren't always indicated in the same way. The IEASYMxx
member only allows comments when enclosed within the bounds of a /* and an
*/; TSOKEY00 only allows comments at the end of all parameters; and members
IGDSMSxx, IPCSPRxx, and IVTPRM00 don't allow any comments.

RECOMMENDATION: Apply the PTF and start adding comments to these
long-neglected parmlib members.
=

I hope this help,
Cheryl

Cheryl Watson
Watson & Walker, Inc.
www.watsonwalker.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Feller, Paul
Sent: Tuesday, August 23, 2016 9:43 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Comments in SYS1.PARMLIB

I thought there was a push by IBM to allow comments in all members.  I
thought the last few members that could not have comments now allow
comments.  As an example I know the COMMNDxx member did not allow comments,
but now it does.  I know the way you put in comments does vary from member
to member.

Thanks..

Paul Feller
AGT Mainframe Technical Support

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Vernooij, Kees (ITOPT1) - KLM
Sent: Tuesday, August 23, 2016 08:26
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Comments in SYS1.PARMLIB

This is because there is no SYS1.PARMLIB owner and interpreter. Each member
has its own owner with its own syntax rules and syntax interpreter. I
presume it is (also here) impossible to have all the labs agree on one set
of rules.

Kees.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Dyck, Lionel B. (TRA)
Sent: 23 August, 2016 15:13
To: 

Re: Comments in SYS1.PARMLIB

[Tom Conley]

On 8/23/2016 9:10 AM, Richards, Robert B. wrote:

This has probably been asked before, but a quick search of the archives did not 
yield the results I was looking for.

Do all members of SYS1.PARMLIB now support /*  */  commenting?

z/OS' 2.1 and 2.2 installed.

Bob



This was one of our big SHARE requirements and we worked hard at it. 
You should be able to put comments in any SYS1.PARMLIB member now.  If 
you find a member that's not supported, please let us know.


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: PTF order fulfillment issues and getting HOLDDATA

[Kurt Quackenbush]

On 8/23/2016 5:52 AM, Vince Getgood wrote:


To resolve this, in my client data, I had to move the data between the  
 tags BETWEEN the   tags.

Before change: -

-v -f "//'DATA.SET.NAME'" 




I don't see how this ever worked, as I get a syntax error when 
 falls outside the  tag.  But in any case, I'm glad 
you got it to work.


Kurt Quackenbush -- IBM, SMP/E Development

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

Re: Comments in SYS1.PARMLIB

[Nims,Alva John (Al)]

Remember the OLD picture of a "Tree Swing Designed by Committee!"

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 Behalf 
Of Rob Schramm
Sent: Tuesday, August 23, 2016 9:48 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Comments in SYS1.PARMLIB

I am sure there was / is.. but apparently standards are inconsistent other than 
what is documented member by member.

Rob Schramm

On Tue, Aug 23, 2016, 9:43 AM Feller, Paul 
wrote:

> I thought there was a push by IBM to allow comments in all members.  I 
> thought the last few members that could not have comments now allow 
> comments.  As an example I know the COMMNDxx member did not allow 
> comments, but now it does.  I know the way you put in comments does 
> vary from member to member.
>
> Thanks..
>
> Paul Feller
> AGT Mainframe Technical Support
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Vernooij, Kees (ITOPT1) - KLM
> Sent: Tuesday, August 23, 2016 08:26
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Comments in SYS1.PARMLIB
>
> This is because there is no SYS1.PARMLIB owner and interpreter. Each 
> member has its own owner with its own syntax rules and syntax interpreter.
> I presume it is (also here) impossible to have all the labs agree on 
> one set of rules.
>
> Kees.
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Dyck, Lionel B. (TRA)
> Sent: 23 August, 2016 15:13
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Comments in SYS1.PARMLIB
>
> Sadly no
>
>
> --
> 
> 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 Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Richards, Robert B.
> Sent: Tuesday, August 23, 2016 8:11 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [EXTERNAL] Comments in SYS1.PARMLIB
>
> This has probably been asked before, but a quick search of the 
> archives did not yield the results I was looking for.
>
> Do all members of SYS1.PARMLIB now support /*  */  commenting?
>
> z/OS' 2.1 and 2.2 installed.
>
> Bob
>
> --
> 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 information, services and offers, please visit our web site:
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.klm.com=DQIF
> Ag=9g4MJkl2VjLjS6R4ei18BA=eUhu3PeeWy6RTndlJVKembFjFsvwCa8eeU_gm45N
> yOc=jxny6YsC6RioMY8630Lu5CRHRmeQTyBBluARUP3_NGI=LHCFuRbZpRcIsVd7Uv
> pDSerOhMKCx2pvUh9G1aPoOvE= . This e-mail and any attachment may 
> contain confidential and privileged material intended for the 
> addressee only. If you are not the addressee, you are notified that no 
> part of the e-mail or any attachment may be disclosed, copied or 
> distributed, and that any other action related to this e-mail or 
> attachment is strictly prohibited, and may be unlawful. If you have 
> received this e-mail by error, please notify the sender immediately by 
> return e-mail, and delete this message.
>
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or 
> its employees shall not be liable for the incorrect or incomplete 
> transmission of this e-mail or any attachments, nor responsible for any delay 
> in receipt.
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal 
> Dutch
> Airlines) is registered in Amstelveen, The Netherlands, with 
> registered number 33014286
> 
>
>
> --
> 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
>
-- 

Rob Schramm

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

Re: PTF order fulfillment issues and getting HOLDDATA

[Nims,Alva John (Al)]

Since you got the answer you needed, I thought I would point out that IBM's FTP 
command searches for "FTP.DATA" differently if the FTP command is invoked from 
"TSO Shell" or "z/OS Unix Shell" according to " z/OS Communications Server: IP 
User's Guide and Commands" and the SMP/e invocation of FTP is from the "z/OS 
Unix Shell".  I got around the problem by creating a ".FTP.DATA" with 
among other things set:
SECURE_MECHANISM  TLS
&
TLSRFCLEVELRFC4217

I was then able to receive PTFs and HOLDDATA.

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 Behalf 
Of Vince Getgood
Sent: Tuesday, August 23, 2016 5:53 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: PTF order fulfillment issues and getting HOLDDATA

Don't know if this will help anybody else out, but I had problems receiving a 
PTF today using SMP/e orderserver, client and FTP data that had worked since I 
started here.

Looking at the output, it seemed that the IBM site was no longer using my FTP 
data dataset.  It was looking for /etc/ftp.data, which doesn't exist, and then 
went to TCPIP.FTP.DATA, which does exist, but is not set up for internet 
delivery.

To resolve this, in my client data, I had to move the data between the 
  tags BETWEEN the   tags. 

Before change: -

-v -f "//'DATA.SET.NAME'" 
 


After change: -

 
-v -f "//'SMPE.CONFIG.FTP.DATA.OPTIONS'" 
 

This worked for me. 

--
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: Comments in SYS1.PARMLIB

[Rob Schramm]

I am sure there was / is.. but apparently standards are inconsistent other
than what is documented member by member.

Rob Schramm

On Tue, Aug 23, 2016, 9:43 AM Feller, Paul 
wrote:

> I thought there was a push by IBM to allow comments in all members.  I
> thought the last few members that could not have comments now allow
> comments.  As an example I know the COMMNDxx member did not allow comments,
> but now it does.  I know the way you put in comments does vary from member
> to member.
>
> Thanks..
>
> Paul Feller
> AGT Mainframe Technical Support
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Vernooij, Kees (ITOPT1) - KLM
> Sent: Tuesday, August 23, 2016 08:26
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Comments in SYS1.PARMLIB
>
> This is because there is no SYS1.PARMLIB owner and interpreter. Each
> member has its own owner with its own syntax rules and syntax interpreter.
> I presume it is (also here) impossible to have all the labs agree on one
> set of rules.
>
> Kees.
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Dyck, Lionel B. (TRA)
> Sent: 23 August, 2016 15:13
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Comments in SYS1.PARMLIB
>
> Sadly no
>
>
> --
> 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 Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Richards, Robert B.
> Sent: Tuesday, August 23, 2016 8:11 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [EXTERNAL] Comments in SYS1.PARMLIB
>
> This has probably been asked before, but a quick search of the archives
> did not yield the results I was looking for.
>
> Do all members of SYS1.PARMLIB now support /*  */  commenting?
>
> z/OS' 2.1 and 2.2 installed.
>
> Bob
>
> --
> 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 information, services and offers, please visit our web site:
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.klm.com=DQIFAg=9g4MJkl2VjLjS6R4ei18BA=eUhu3PeeWy6RTndlJVKembFjFsvwCa8eeU_gm45NyOc=jxny6YsC6RioMY8630Lu5CRHRmeQTyBBluARUP3_NGI=LHCFuRbZpRcIsVd7UvpDSerOhMKCx2pvUh9G1aPoOvE=
> . This e-mail and any attachment may contain confidential and privileged
> material intended for the addressee only. If you are not the addressee, you
> are notified that no part of the e-mail or any attachment may be disclosed,
> copied or distributed, and that any other action related to this e-mail or
> attachment is strictly prohibited, and may be unlawful. If you have
> received this e-mail by error, please notify the sender immediately by
> return e-mail, and delete this message.
>
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
> employees shall not be liable for the incorrect or incomplete transmission
> of this e-mail or any attachments, nor responsible for any delay in receipt.
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
> Airlines) is registered in Amstelveen, The Netherlands, with registered
> number 33014286
> 
>
>
> --
> 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
>
-- 

Rob Schramm

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

Re: Comments in SYS1.PARMLIB

[Feller, Paul]

I thought there was a push by IBM to allow comments in all members.  I thought 
the last few members that could not have comments now allow comments.  As an 
example I know the COMMNDxx member did not allow comments, but now it does.  I 
know the way you put in comments does vary from member to member.

Thanks..

Paul Feller
AGT Mainframe Technical Support

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Vernooij, Kees (ITOPT1) - KLM
Sent: Tuesday, August 23, 2016 08:26
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Comments in SYS1.PARMLIB

This is because there is no SYS1.PARMLIB owner and interpreter. Each member has 
its own owner with its own syntax rules and syntax interpreter. I presume it is 
(also here) impossible to have all the labs agree on one set of rules.

Kees.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Dyck, Lionel B. (TRA)
Sent: 23 August, 2016 15:13
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Comments in SYS1.PARMLIB

Sadly no


--
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 Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Richards, Robert B.
Sent: Tuesday, August 23, 2016 8:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Comments in SYS1.PARMLIB

This has probably been asked before, but a quick search of the archives did not 
yield the results I was looking for.

Do all members of SYS1.PARMLIB now support /*  */  commenting?

z/OS' 2.1 and 2.2 installed.

Bob

--
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 information, services and offers, please visit our web site: 
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.klm.com=DQIFAg=9g4MJkl2VjLjS6R4ei18BA=eUhu3PeeWy6RTndlJVKembFjFsvwCa8eeU_gm45NyOc=jxny6YsC6RioMY8630Lu5CRHRmeQTyBBluARUP3_NGI=LHCFuRbZpRcIsVd7UvpDSerOhMKCx2pvUh9G1aPoOvE=
 . This e-mail and any attachment may contain confidential and privileged 
material intended for the addressee only. If you are not the addressee, you are 
notified that no part of the e-mail or any attachment may be disclosed, copied 
or distributed, and that any other action related to this e-mail or attachment 
is strictly prohibited, and may be unlawful. If you have received this e-mail 
by error, please notify the sender immediately by return e-mail, and delete 
this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286



--
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: Comments in SYS1.PARMLIB

[Elardus Engelbrecht]

Richards, Robert B. wrote:

>This has probably been asked before, but a quick search of the archives did 
>not yield the results I was looking for.

>Do all members of SYS1.PARMLIB now support /*  */  commenting?

No. There is only one standard with this name: 'NO STANDARDS'   ;-)


IEASYSxx has this:
DIAG=00,  COMMENT

ARCCMDxx:
/* COMMENT */
SETSYS ...

ADYSETxx:

* COMMENT
  DAE ...

Oh, not all members have the same set of continuation syntax. 

Some members have this:

 STATEMENT KEYWORD,

Others like ARCCMDxx has this:

SETSYS - 
  NODEBUG

I could go on...

Good luck trying to untangle this...

Groete / Greetings
Elardus Engelbrecht

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

Re: Mainframe's security assessments costs

[Elardus Engelbrecht]

Costin Enache wrote:

>Why you need the assessment for? If you need it for some certification / legal 
>purpose, then there are cheap, not too technically advanced solutions out 
>there. If you are actually looking into detecting and addressing security 
>issues, then it gets complicated :)

Good first question! Ask that 'WHY' question and ask it again. ;-)


>... a penetration test, ... 

From where? Costs can vary wildly depending on type of Pen Test and origin of 
those tests (within mainframe or from outside) and usage of whatever utilities.


>Once you have decided what type of assessment you are looking for, you should 
>define the scope of the project: ...

Another good question: What is the scope? z/OS? Application? Mainframe Network 
and/or other network connecting to the mainframe? OMVS setup? RACF or ESM? etc.


>There will be plenty of companies claiming to do mainframe security 
>assessments, coming from the penetration testing field, with little if any 
>mainframe experience, who would fire some tools, maybe crash some things, give 
>you an absurd, pointless report. 

Indeed. One PT in the past resulted in heavy network load. Next time, 'they' 
have to arrange for a date/time *before* they repeat their PT. 'They' tried 
once to repeat their PT without formal approval and later complained why we 
blocked their system to access our mainframe. Tsk, tsk, tsk. Too bad, too sad.


>Maybe it will be cheap, but useless. 

Those cheapies asked me *why*, oh *why* is there not an Anti-Virus package and 
Malicous Software detection installed on z/OS (excluding Linux and similar 
animals of course).


>Before selecting a provider, make sure you talk to them, interview the 
>auditors and make sure they are familiar with mainframes, ...

You can also ask them, if they find a problem, what would *they* suggest to fix 
it. It will demonstrate their real skills.

Groete / Greetings
Elardus Engelbrecht

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

Re: Comments in SYS1.PARMLIB

[Vernooij, Kees (ITOPT1) - KLM]

This is because there is no SYS1.PARMLIB owner and interpreter. Each member has 
its own owner with its own syntax rules and syntax interpreter. I presume it is 
(also here) impossible to have all the labs agree on one set of rules.

Kees.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Dyck, Lionel B. (TRA)
Sent: 23 August, 2016 15:13
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Comments in SYS1.PARMLIB

Sadly no


--
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 Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Richards, Robert B.
Sent: Tuesday, August 23, 2016 8:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Comments in SYS1.PARMLIB

This has probably been asked before, but a quick search of the archives did not 
yield the results I was looking for.

Do all members of SYS1.PARMLIB now support /*  */  commenting?

z/OS' 2.1 and 2.2 installed.

Bob

--
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 information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286



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

Re: Comments in SYS1.PARMLIB

[Dyck, Lionel B. (TRA)]

Sadly no


--
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 Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Richards, Robert B.
Sent: Tuesday, August 23, 2016 8:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Comments in SYS1.PARMLIB

This has probably been asked before, but a quick search of the archives did not 
yield the results I was looking for.

Do all members of SYS1.PARMLIB now support /*  */  commenting?

z/OS' 2.1 and 2.2 installed.

Bob

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

Comments in SYS1.PARMLIB

[Richards, Robert B.]

This has probably been asked before, but a quick search of the archives did not 
yield the results I was looking for.

Do all members of SYS1.PARMLIB now support /*  */  commenting?

z/OS' 2.1 and 2.2 installed.

Bob

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

Re: Loading Java dump into IPCS

[Barkow, Eileen]

-X options would probably go into the the STDENV IBM_JAVA_OPTIONS parm

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Janet Graff
Sent: Monday, August 22, 2016 8:05 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Loading Java dump into IPCS

When running from the USS command line I can specifiy -Xdump:none and suppress 
the Java dumps and traces.  Then if I get an abend I get the CEEDUMP which is 
much more useful.  Where do I specify -Xdump:none in the EXEC=JVMLDM66 JCL?  
Does it go in the STDENV or is it an argument?

Janet

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



This e-mail, including any attachments, may be confidential, privileged or 
otherwise legally protected. It is intended only for the addressee. If you 
received this e-mail in error or from someone who was not authorized to send it 
to you, do not disseminate, copy or otherwise use this e-mail or its 
attachments. Please notify the sender immediately by reply e-mail and delete 
the e-mail from your system.

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

Re: Mainframe's security assessments costs

[Jack J. Woehr]

Costin Enache wrote:

If you are actually looking into detecting and addressing security issues, then 
it gets complicated:)


The different between cloaking the gluteus and actual forensics!

--
Jack J. Woehr # Science is more than a body of knowledge. It's a way of
www.well.com/~jax # thinking, a way of skeptically interrogating the universe
www.softwoehr.com # with a fine understanding of human fallibility. - Carl Sagan

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

Re: Survey question: what do you specify for HVCOMMON?

[Charles Mills]

REAL memory? (Other than very occasional backing store?)

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Graham Harris
Sent: Monday, August 22, 2016 7:19 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Survey question: what do you specify for HVCOMMON?

As we have no plans to use HIS sampling (which I presume is what makes use of 
the data), it seemed an unnecessary waste of real memory.  It is a decision 
that is easily reversed if this data may become valuable in the future.

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

Re: PTF order fulfillment issues and getting HOLDDATA

[Vince Getgood]

Don't know if this will help anybody else out, but I had problems receiving a 
PTF today using SMP/e orderserver, client and FTP data that had worked since I 
started here.

Looking at the output, it seemed that the IBM site was no longer using my FTP 
data dataset.  It was looking for /etc/ftp.data, which doesn't exist, and then 
went to TCPIP.FTP.DATA, which does exist, but is not set up for internet 
delivery.

To resolve this, in my client data, I had to move the data between the 
  tags BETWEEN the   tags. 

Before change: -

-v -f "//'DATA.SET.NAME'" 
 


After change: -

 
-v -f "//'SMPE.CONFIG.FTP.DATA.OPTIONS'" 
 

This worked for me.

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

Re: Mainframe's security assessments costs

[Costin Enache]

Hi,

Some topics that we had to address when performing mainframe security 
assessments:

Why you need the assessment for? If you need it for some certification / legal 
purpose, then there are cheap, not too technically advanced solutions out 
there. If you are actually looking into detecting and addressing security 
issues, then it gets complicated :)

The possible range of services on this topic is huge. You should decide what 
you want to have, what kind of security assessment you are looking for - for 
example you have the "classic" mainframe security audits, more like security 
reviews, where some programs are used to list and catalog the authorizations, 
profiles, etc., interview personnel and determine the access needs, etc. You 
can alternatively look for a combination of the above and a penetration test, 
actively searching and exploiting security issues found in your environment. Or 
you can have a PT targeting the mainframe environment, where you can chose the 
"white box" (i.e. fully disclosed, insider view) or the "black box" (i.e. 
simulation of a real opportunistic attack) perspectives, each with its own 
pluses and minuses.

Once you have decided what type of assessment you are looking for, you should 
define the scope of the project: are you looking into an o/s-only assessment 
(i.e. basic z/OS or z/VM components, maybe RACF, USS, and some "standard" 
subsystems), or maybe an application-oriented audit, where you select one or 
more applications that might be mainframe-only or might include other 
components to audit going from the o/s to the application layer (say you use 
the mf for banking, ATMs, credit card operations, you would select the 
subsystems and applications for the business critical operations in this 
respect). You could limit the assessment to one or more instances/LPARs, 
subsystems, ... include or not other components such as SE/HMC in the scope.

Most often, event a narrowed-down scope gets to be too large for a complete 
security assessment, and a "limited" version is performed, either by limiting 
the total man/days to a fixed amount calculated based on a budget, or by 
sampling, reviewing the results, then shifting the focus to the areas found to 
be suffering from security issues.

There will be plenty of companies claiming to do mainframe security 
assessments, coming from the penetration testing field, with little if any 
mainframe experience, who would fire some tools, maybe crash some things, give 
you an absurd, pointless report. Maybe it will be cheap, but useless. Before 
selecting a provider, make sure you talk to them, interview the auditors and 
make sure they are familiar with mainframes, maybe examine their research 
environment to see of they have a proper, recent mf environment to do testing, 
and check for specific references in the mainframe field, not just generic 
penetration testing. 

As for the costs, expect to pay in the range of 1500 - 2000 Euro for a man/day 
in EU. We've never had a project to perform a complete security assessment of a 
mainframe environment, maybe other had this and can share approximate sizing; 
usually we've seen application-oriented ones, o/s layer and basic subsystems, 
or by sampling. The size of such projects grossly goes from 40 to 100 man/days, 
depending on the actual scoping. This is very imprecise, but I guess you wanted 
to see some numbers as well.

Regards,
Costin


On Mon, 15/8/16, x ksi  wrote:

 Subject: Mainframe's security assessments costs
 To: IBM-MAIN@LISTSERV.UA.EDU
 Date: Monday, 15 August, 2016, 1:51
 
 Hey group. I was wondering if some of
 you could share some information
 about the costs various companies charged you for performing
 security
 assessment of your mainframes? At this point literally any
 information
 will be valuable (e.g. hourly rate, particular engagement
 cost, order
 of magnitude for this type of engagements etc.). From what I
 can tell
 there are companies providing such services but their prices
 seem to
 be a one big mystery. Having even a rough estimation would
 allow to
 better choose between various providers. Thank you in
 advance.
 
 
 Kind regards,
 Filip
 
 --
 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