from:"R.S."

Re: Email Providers

2021-01-25 Thread R.S.

Now I can answer: I hate this disclaimer. I was almost ready to switch to 
private email when they started with this cr*p, but 1. I'm lazy, 2. other 
people have similar disclaimers, so I felt not so guilty. 

Regarding gmail - I already have gmail account and I don't want to use it for 
other activities. I attempted to use second account, but this provide 
complexity.

However I have no luck - yahoo is bad, aol is the same company so I won't even 
try. Protonmail claim they don't support POP3/IMAP, and GMX registration just 
ended with some error.  

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

Re: How to validate mount points for IPLs

2021-01-24 Thread R.S.

Well, In my opinion there is no such tool or process. 
Few remarks:
1. Assuming you have such checker and just tested BPXPRM member. Few minutes 
later things may change - someone can delete or rename some ZFS. Or just modify 
BPXPRM.
2. "Prior IPL" is a little bit ambigous. Does it mean the system is down? Or it 
is up and you want to re-IPL it? For non-IPLed system you would have to access 
datasets from other (tech) system. It is possible, but a little bit hard for 
VSAM ZFS. Of course "before re-IPL" scenario is much simpler. 
3. It is not matter of ZFS dataset names and typos. Or missing datasets. What 
about mount point? Mount point, a path ma be nonexistent - this can be checked 
before re-IPL. However mount point can be simply wrong. 

My advices:
1. Simply protect BPXPRM against hasty changes. It's obvious, just track all 
the updates. Comments are your friend. 
2. The above simplify and reduce effort needed to check it manually. Just check 
latest changes, especially changes made after last IPL.
3. Keep it simple. Documentation would help.
4. One can create the following REXX script: read every filesystem name and 
list it i.e. using listdsi. Also read every mount point and check its existence 
in z/OS Unix.


HTH

--
Radoslaw Skorupka
(currently unemployed)
Lodz, Poland

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

Re: TWS replacements

2021-01-23 Thread R.S.

IMHO it would be hard to get something cheaper and not worse. Of course prices 
depend on contracts and your need may be satisfied with very basic tool. 

--
Radoslaw Skorupka
(from new mail)

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

Re: TSO RECEIVE and System Determined Blksize (was: TSO XMIT and no member list)

2021-01-20 Thread R.S.


W dniu 20.01.2021 o 20:35, Seymour J Metz pisze:

Whoosh! What is in dispute is the ludicrous claim '"Illegal" from SMP/E point 
of view'.  Aps have *never* been Illegal from SMP/E point of view, or even from the POV 
of the free SMP versions.


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


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
R.S. [r.skoru...@bremultibank.com.pl]
Sent: Wednesday, January 20, 2021 1:02 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: TSO RECEIVE and System Determined Blksize (was: TSO XMIT and no 
member list)

W dniu 20.01.2021 o 18:43, Seymour J Metz pisze:

Nonsense, there's nothing illegal about ++ ZAP.

SMP does what you would expect, including warning you of conflicting service.


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


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
R.S. [r.skoru...@bremultibank.com.pl]
Sent: Wednesday, January 20, 2021 12:32 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: TSO RECEIVE and System Determined Blksize (was: TSO XMIT and no 
member list)

W dniu 20.01.2021 o 18:10, Seymour J Metz pisze:

There are ZAPs to change it in original IBM code.
"Illegal" from SMP/E point of view

No.


Yes.

--
Radoslaw Skorupka
Lodz, Poland

Nonsense, there are ZAPs to change it.



What is in dispute is written in the messages.
You cited TWO sentences and commented it "No." Can it be shorter and 
more ambigous?
However YES, there are ZAPs to change it in original IBM code. Aren't 
there?

Regarding the second sentence - I used quotes. Why? What could it mean?
Maybe this: ZAP can be done without SMP/E, just load module 
modification. Can't it be? Caution: I don't say it is good practise.
In that case such ZAP is somehow illegal from SMP/E point of view. Isn't 
it?
And last, but not least - I also wrote it is not supported by IBM. Maybe 
it is not big issue, but ...isn't it true?


Oh, BTW, some answers: No, Yes, You're wrong, PKB, ABC, XYZ. Or maybe 
single letter ones?


BTW2: I used SYSOUT(n) (n is some class) and it fills the expectations - 
almost all IEBCOPY output is redirected to JES2. Almost all, because 
some PDSes caused RC=4 and some messages were available on the screen. 
Unfortunately RC=4 from IEBCOPY caused XMIT to fail.


--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

--
For IBM-MAIN subscribe / signoff / arc

Re: TSO RECEIVE and System Determined Blksize (was: TSO XMIT and no member list)

2021-01-20 Thread R.S.


W dniu 20.01.2021 o 18:43, Seymour J Metz pisze:

Nonsense, there's nothing illegal about ++ ZAP.

SMP does what you would expect, including warning you of conflicting service.


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


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
R.S. [r.skoru...@bremultibank.com.pl]
Sent: Wednesday, January 20, 2021 12:32 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: TSO RECEIVE and System Determined Blksize (was: TSO XMIT and no 
member list)

W dniu 20.01.2021 o 18:10, Seymour J Metz pisze:

There are ZAPs to change it in original IBM code.
"Illegal" from SMP/E point of view

No.


Yes.

--
Radoslaw Skorupka
Lodz, Poland


Nonsense, there are ZAPs to change it.

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: TSO RECEIVE and System Determined Blksize (was: TSO XMIT and no member list)

2021-01-20 Thread R.S.


W dniu 20.01.2021 o 18:10, Seymour J Metz pisze:

There are ZAPs to change it in original IBM code.
"Illegal" from SMP/E point of view

No.


Yes.

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: TSO RECEIVE and System Determined Blksize (was: TSO XMIT and no member list)

2021-01-20 Thread R.S.


W dniu 20.01.2021 o 17:03, Wendell Lovewell pisze:

Radoslaw,

Could you please elaborate on your comment "never solved issue like non-SDB (system 
determined blocksize) in XMIT and RECEIVE command"?

I have been having an issue with TSO RECEIVE (and a program that also calls IEBCOPY) when 
SDB is "Y".  IEBCOPY is having some sort of problem and displaying this message:

IEB1139W THE OUTPUT DATA SET BLOCK SIZE IS BEING REDUCED FROM 32720 TO 27920 
BYTES.  ANY EXISTING PHYSICAL RECORDS
  LONGER THAN 27920 BYTES ARE FAT BLOCKS AND MAY CAUSE I/O ERRORS.

and ending with a return code of 4.  The dataset being RECEIVEd is actually 
fine, as the LRECL is always less than 27920 (80 in this case).  But RECEIVE 
sees the RC=4 from IEBCOPY and ends with RC=12.

IBM currently has case number TS004689510 open for this, but I assumed it was a 
new issue although I only have SDB=Y on right now for testing.

Any thoughts?

~ Wendell Lovewell


I mean the following:
try the command
XMIT NODE.USER DA(SOME.PDS) OUTDA(XMIT.FILE)
and you will get XMIT.FILE as PS FB LRECL=80,BLKSIZE=3120 and that 
blocksize does not look good nowadays.
We have SDB for decades, but not here. There are ZAPs to change it in 
original IBM code. "Illegal" from SMP/E point of view and no supported 
by IBM.
Not to mention last "few years" we have 3390 geometry with very few 
exceptions. Nevermind, the only exception we can meet can be 3380. I 
would bet it is possible to use a little bigger blocksize for both of 
them if one wants to still support 47k trk.





--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: TSO XMIT and no member list

2021-01-20 Thread R.S.


Thank you everyone for your answers.
It seems I can redirect SYSOUT to DD DUMMY for a while.
In fact I wanted to switch off IEBCOPY reporting, AFAIR it was LIST=NO. 
It can be specified in PARM field or as an optional parameter of COPY 
command in SYSIN.
It is not exactly the same as whole sysout redirected to DUMMY, but 
sometimes you won't get exactly what you want. ;-)

Thank you again.

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: TSO XMIT and no member list

2021-01-19 Thread R.S.


W dniu 20.01.2021 o 01:23, Paul Gilmartin pisze:

On Wed, 20 Jan 2021 00:55:59 +0100, R.S. wrote:


I want to switch off member list when TSO XMIT ... DA(SOME.PDS) is running?
I just want to issue the command and I don't want to see loong
member list on the screen.
Any clue?


OUTTRAP?
Well, I think it would hide all messages. However it would be good to 
still see begin and end of step.
Antoher way I know is to run REXX in batch (why not IEBCOPY in JCL? - 
that's another story) and simply ignore output.


It seems quite obvious and never solved issue like non-SDB (system 
determined blocksize) in XMIT and RECEIVE command.


--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

TSO XMIT and no member list

2021-01-19 Thread R.S.


I want to switch off member list when TSO XMIT ... DA(SOME.PDS) is running?
I just want to issue the command and I don't want to see loong 
member list on the screen.

Any clue?

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: VSAM file discrepancies

2021-01-19 Thread R.S.


W dniu 19.01.2021 o 17:22, Cameron Conacher pisze:

A KSDS with duplicate full primary key values?
Are you sure?


I'm sure it is possible.
VSAM is just set of data... Data set on disk. ;-)
Yes, it is hard to have duplicate key WHEN USING VSAM (access method).
However is is enough to use CI mode or just ditto or file manager to 
make things interesting.
However I admit - I cannot imagine how it could happen when using 
"regular" application.


--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: EOM for z hardware clarification

2021-01-18 Thread R.S.


Well said.
However I have different observations of real world. It can be computer, 
dasd array, car, truck, airplane, etc.
I even know cases when a leasing company is owned by leasing client. 
Sometimes bank lend money to (its own) leasing company just to lease 
something from that company.

Of course I do not operate in US, so YMMV.

BTW: leasing, CAPEX and OPEX are slightly off-topic. ;-)

--
Radoslaw Skorupka
Lodz, Poland






W dniu 18.01.2021 o 14:05, Joe Monk pisze:

"CAPEX can be converted to OPEX i.e. by using leasing services."

The lease must be a fair market value lease, so that title does not pass.
Only then is it  considered OPEX.

If it's a dollar buyout lease, then its a CAPEX lease and must  be
accounted for as CAPEX.

Joe

On Mon, Jan 18, 2021 at 6:46 AM R.S.  wrote:


W dniu 18.01.2021 o 13:28, Joe Monk pisze:

"2. EOM and EOS are important, but IMHO prices are more important. In
many cases it is cheaper to replace machine than to buy service contract
for existing (old) one. And it is rather cheaper to buy newer model even
if new and new-1 are available."

The purchase  of hardware is CAPEX. The purchase of a service contract is
OPEX. OPEX is an expense and affects income, therefore you do not  have

to

pay income tax on it. CAPEX affects fixed assets and there are taxes to

be

paid on it.

There is a point where it is less expensive to replace, say a model with
one that is newer (maybe a z13 with  a z16). But in general, it is less
expensive to maintain an existing piece of equipment  than to buy a new

one

   (depreciation and all).

CAPEX can be converted to OPEX i.e. by using leasing services. There are
also other tricks.
Regarding prices - I do not have to convince anyone, but ...I used to
buy mainframes and I simply see IBM offerings. Depending on time
perspective *usually* it is more effective (cheaper) to buy new
equipment than buy service for existing one. My advice: buying new
hardware is the best time to think about service for all life of it.
Extending support after first year tend to be more expensive, especially
when new machine is available.

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: EOM for z hardware clarification

2021-01-18 Thread R.S.


W dniu 18.01.2021 o 13:28, Joe Monk pisze:

"2. EOM and EOS are important, but IMHO prices are more important. In
many cases it is cheaper to replace machine than to buy service contract
for existing (old) one. And it is rather cheaper to buy newer model even
if new and new-1 are available."

The purchase  of hardware is CAPEX. The purchase of a service contract is
OPEX. OPEX is an expense and affects income, therefore you do not  have to
pay income tax on it. CAPEX affects fixed assets and there are taxes to be
paid on it.

There is a point where it is less expensive to replace, say a model with
one that is newer (maybe a z13 with  a z16). But in general, it is less
expensive to maintain an existing piece of equipment  than to buy a new one
  (depreciation and all).


CAPEX can be converted to OPEX i.e. by using leasing services. There are 
also other tricks.
Regarding prices - I do not have to convince anyone, but ...I used to 
buy mainframes and I simply see IBM offerings. Depending on time 
perspective *usually* it is more effective (cheaper) to buy new 
equipment than buy service for existing one. My advice: buying new 
hardware is the best time to think about service for all life of it. 
Extending support after first year tend to be more expensive, especially 
when new machine is available.


--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: EOM for z hardware clarification

2021-01-18 Thread R.S.

W dniu 18.01.2021 o 10:55, Peter pisze:

Hello All,

Just curious to understand what is the minimum duration for the z hardware
to be from withdrawn from marketing ?

Are there any specific factor IBM follows ?

There is excellent paper describing all the dates (GA, EOM, EOS).
I found the link:
https://www.ibm.com/support/pages/system/files/inline-files/IBM_Mainframe_Life_Cycle_History_V2.6_-_Oct_13_2020.pdf

Few remarks
1. There is no long term comitment saying, let's say z16 will be
available for minimum 5 years. Everytime this is decision of IBM.
2. EOM and EOS are important, but IMHO prices are more important. In
many cases it is cheaper to replace machine than to buy service contract
for existing (old) one. And it is rather cheaper to buy newer model even
if new and new-1 are available.
3. There are other issues, like upgrade availability. Usually IBM first
close "physical" upgrades, that means new hardware elements (cards,
DRAWERs, etc.) Later IBM close microcode upgrades - this is reasonable,
since they do not deliver anything physically.

4. There are independent service providers.

--
Radoslaw Skorupka
Lodz, Poland

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo

If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection
with correspondence with us. We process your data for purposes resulting from
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: JCL to tar USS directory

2021-01-14 Thread R.S.


W dniu 14.01.2021 o 16:00, Bill Giannelli pisze:

can anyone provide JCL to tar a USS directory?
thanks
Bill


Correction:
//K10  EXEC PGM=BPXBATCH,PARM='PGM /bin/tar -?'
//STDOUT   DD SYSOUT=*
//STDERR   DD SYSOUT=*

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: JCL to tar USS directory

2021-01-14 Thread R.S.


W dniu 14.01.2021 o 16:00, Bill Giannelli pisze:

can anyone provide JCL to tar a USS directory?
thanks



//K10  EXEC PGM=BPXBATCH,PARM='SH tar parameterscd;ls'
//STDOUT   DD SYSOUT=*
//STDERR   DD SYSOUT=*

ls is redundant, it is just as example of second command within the step.

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: Starting a started task from a started task

2021-01-14 Thread R.S.


W dniu 14.01.2021 o 15:57, Horne, Jim pisze:

Hi all,

This may sound like a stupid question but is there a way to start a second 
started task from a running one when the currently running one completes.  I 
know how to submit a batch job from a final step of a started task but I don't 
know how to do the same sort of thing to initiate another started task.


It depends.
The simplest way is to use JCL facilities.
Your started task can have last step, which can submit batch job, which 
in turn can issue a COMMAND, the command can be START STC.

A little bit Ruby Goldberg, but it works.

Other way is to use one of the tools from CBT to issue a command. In 
that scenario you last step in started task run the program. Program 
parameters contain you command - START STC.


I would also think about SystemREXX, but I have to solution here.

HTH

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: Code to verify LOGON password

2021-01-12 Thread R.S.


W dniu 12.01.2021 o 06:42, Timothy Sipples pisze:

Radoslaw Skorupka wrote:

That's what we call brute force attack.
There is no way to protect against it ...or maybe there are some
things to help.
1. Do not give your RACF db to hackers. Never.
2. Enforce periodic password change.
3. Use KDFAES.
4. Use passphrases.

Here are some more examples for your list:

5. Don't grant overly generous permissions. Revoke permissions faithfully
and promptly when required.

6. IBM Z Multi-Factor Authentication.

7. Use excellent data access management and Security Information and Event
Management (SIEM) solutions.

8. "Stay sharp." Invest in talented security professionals, including in
their ongoing skills development. Hire other talented security people to
conduct periodic audits.

9. Stay at least reasonably current with software releases, including z/OS
releases. Have and follow a reasonable preventive maintenance plan,
including for security and integrity updates.

10. Use strong, properly implemented network encryption so that
credentials aren't flying across any LAN or WAN in cleartext. z/OS
Encryption Readiness Technology (zERT), a standard feature included with
the base z/OS operating system starting with z/OS 2.3, can help identify
gaps.


Good points. IMHO the most important is 8. Of course it is not about 
RACF, it is about people. However no technology would help if the only 
effort was to buy it, but no necessaruly well implemented. Uneducated, 
lazy people, overloaded staff, lack of interest from management lead to 
mistakes, even serious neglects.


--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: Code to verify LOGON password

2021-01-12 Thread R.S.

W dniu 11.01.2021 o 17:44, Charles Mills pisze:

https://en.wikipedia.org/wiki/John_the_Ripper

There is a downloadable plugin for RACF -- old RACF hashing only, I *think*.

@R.S. writes

1. Do not give your RACF db to hackers. Never.

No one "gives" their RACF DB to anyone (I would hope). The problem -- and everyone
reading this who is not sure about their RACF DB should go check right now -- is UACC or USERID(*)
READ access to the RACF DB *or its backup*. If I can download your RACF DB and attack it
off-platform I can defeat any "revoke the userid after 'n' tries" that you have in place.

Charles,
You missed the fine print between the lines : IRONY ;-)

Of course matter of backup copies, user revoking, etc. was discussed ad
infinitum. Of course it is important, but a little bit not closely
related to discussed details in this thread.

Regarding the ripper - There is password cracker for z/OS. You need APF
update, dictionaries (or program generating passwords) and cpu cycles.

APF update? Same configuration mistake as READ for RACF db.

Despite of cracker implementation, KDFAES plus passphrases plus
(included in passphrases) rules for password complexity make cracking
much less efficient.

--
Radoslaw Skorupka
Lodz, Poland

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

If you are not the addressee of this message:

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

Re: z/OS holddata per https?

2021-01-12 Thread R.S.

Other solution: just circumvent restrictions. Simply download HOLDDATA 
using private PC and then send it via email. Yes, it is a crime... but 
it works.
Of course it would require some effort to understand that it is possible 
to allow ftp to IBM site, especially limited to few persons which have 
interest to use it. Access to HOLDDATA is valid need and it should be 
processed with no obstacles.


--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: Code to verify LOGON password

2021-01-11 Thread R.S.


That's what we call brute force attack.
There is no way to protect against it ...or maybe there are some things 
to help.

1. Do not give your RACF db to hackers. Never.
2. Enforce periodic password change.
3. Use KDFAES.
4. Use passphrases.

First is obvious.

Effectiveness of the second is disputable, but it rather won't help 
hackers. The idea is to

a) give less time for password cracking.
b) give less time for using of intercepted user/password.
c) give less possibilities to peek co-workers password (next letters).
There is also disadvantage: too complex and too frequently changed 
password lead to yellow stickers.


Third can be surprising for some people, but this method provide much 
more time consuming method of password hashing. Much more is tens of 
thousands. That means brute force attack would take tens of thousands 
times more time. It is still finite, but much longer.


Fourth method provide much more space for passwords. Let's forget about 
social hacking for a while, just "blind" brute force. To simplify - 
8-char password could mean 39^8 combinations (roughly, these 
calculations are not exact). 16-char password is 39^8 * 39^8 - that's 
5 352 009 260 481 times more combinations. And 24-char password gives 
28 644 003 124 274 380 508 351 361 times more.


The above is not exact analysis. Password and passphrase space is 
limited by some rules, but there are also shorter passwords and much 
more lenghts of passphrases - 100,99,98,97,96...11,10,9. A lot of.



My €0.02

--
Radoslaw Skorupka
Lodz, Poland






W dniu 11.01.2021 o 15:39, Tom Brennan pisze:
Isn't there a program someone wrote (talked about here many years ago) 
that can try various passwords until something matches the hashed 
value?  If that's the case, hashing doesn't really do as much good as 
people think it does, once someone gets hold of the RACF dataset of 
course.


On 1/10/2021 7:57 PM, Timothy Sipples wrote:


Here's a pedantic point: RACF doesn't actually know what the user's
password is -- thank goodness. RACF can only determine whether a
particular password or passphrase string mathematically corresponds 
to the

hashed value (derived from previous input) that RACF stores. True, good
hashing functions minimize collisions, and RACF uses good hashing
functions.


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




==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

YADRO mainframes?

2021-01-11 Thread R.S.


I just found some IBM document showin parameters of ...YADRO mainframes.
It is dated 30-04-2017.
Yes, the term "mainframe" is used. There are parameters like MSU, 
keywords like PSLC, zNALC, Coupling Facility, z/OS, z/VSE, etc.


YADRO is russian IT company - that's all I know. I'm even not sure it is 
not coincidence.



Can anyone sched some light on that?

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: Anyone using IBM Cloud Tape Connector?

2021-01-11 Thread R.S.


W dniu 11.01.2021 o 12:07, David Spiegel pisze:

Hi Tim,
You said: "... but there are at least three choices ..."
Other than RACF, ACF2 and TSS are there others?


Yes. However IMHO none of them is active.
Examples:
1. Deadbolt. It was announced, but I don't know if any shop implemented it.
2. PIES. Polish product (pies = dog), offered by Mainframe Ltd. from 
Raszyn, Poland.



--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: Request for help with removing sequence numbers from PDS members

2021-01-11 Thread R.S.


W dniu 11.01.2021 o 10:05, Sean Gleann pisze:

This has almost certainly cropped up before but try as I might, I can't
spot anything obvious in the archives.

I have a need to strip sequence numbers from members in a PDS or PDSE.
The input PDS(E) has DCB characteristics of REFCM=FB,LRECL-80, and contains
an unknown number of members. Of those members, some will have records with
'old data' in character positions 73-80 (that is - sequence numbers, or
whatever remains of them).
I want to be able to copy this input PDS(E) to a new one with the same DCB
info, but all records in all members must have spaces in positions 73-80.

I thought that ICETOOL might be able to do this but as far as I can see,
ICETOOL needs to be told which member names to process. That information is
readily available while developing and testing a solution, but not when the
result is used in a more general scenario.

Can anyone point me at some sort of solution that I might adapt, please?
Perhaps there is something on the CBT tape that might help...


I don't know any tool, but I have some idea how to do it.
Use REXX script.
It's quite simple to get member list and do somethin in a loop until 
last member is processed.

What to do?
Again, I don't know any tool, however it could be feasible to use 
IEBGENER with non-empty SYSIN, ICEMAN, or TSO EDIT, or ISPF EDIT, or 
something else.
Caution: things are simple when you just want to replace position 73-80 
despite of its actual content, that means without checking it.


HTH

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: ZFS using zEDC hardware compression

2021-01-08 Thread R.S.

W dniu 08.01.2021 o 17:46, Paul Gilmartin pisze:

On Fri, 8 Jan 2021 16:07:31 +, Seymour J Metz wrote:

A zFS is stored in a VSAM linear data set. I found "Only extended-format
key-sequenced data sets can be compressed." at
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.idad400/compdta.htm

This is a plausible consequence of not using keys: There's no easy way
to access a given datum.

Well, PS dataset have no keys and they are quite compressible. The devil
is in details of access method and "presentation layer" of compression.
And there are consequences of CI (record, slot) update - it can be less
compressed. So, compressed VSAM should have some kind of DAT (Dynamic
Address Translation) for CI addresses. It is feasible, but quite complex
IMHO.

--
Radoslaw Skorupka
Lodz, Poland

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

If you are not the addressee of this message:

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

Re: ZFS using zEDC hardware compression

2021-01-08 Thread R.S.


I just RTFM. No VSAM dataset can be compressed using zEDC.

Of course VSAM datasets dumped with DFSMSdss may be compressed, because:
a) output dataset is PS, which is eligible for zEDC compression.
b) dss itself can use zEDC to compress data written to output. Such 
dataset can be writted on tape or disk. There is no reason to make it 
zEDC compressible.


--
Radoslaw Skorupka
Lodz, Poland






W dniu 08.01.2021 o 17:20, PINION, RICHARD W. pisze:

That's a definitive answer, thanks.

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Seymour J Metz
Sent: Friday, January 8, 2021 11:08 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ZFS using zEDC hardware compression

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

A zFS is stored in a VSAM linear data set. I found "Only extended-format 
key-sequenced data sets can be compressed." at 
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.idad400/compdta.htm






==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: ZFS using zEDC hardware compression

2021-01-08 Thread R.S.


W dniu 08.01.2021 o 16:00, PINION, RICHARD W. pisze:

Can a ZFS dataset be defined with the DATACLAS zEDC compression option?  I'm 
looking for a way
to reduce the size of our SMPNTS datasets.


I guess YES.
However ...just try it. Create some test ZFS with copression and put 
some txt files there. That will prove a) parameters are accepted, b) 
compression is really working.


--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: Progam directory AD/Cycle C/370

2021-01-06 Thread R.S.


W dniu 06.01.2021 o 09:19, Tom Ross pisze:

BTW: Is there description/list of COBOL versions anywhere?

  I don't know, but I have lists!  Here is the entire history, no names, just
  product ids, but you can kind of tell which is which by the dates.
OS/VS COBOL, VS COBOL II, etc etc
Note: You need fixed-width caharacters to view this table:

  Program  Marketing   Service
  Number   VRM Announced   Available   Withdrawn   Discontinued

  5740-CB1 1.02.4  1974/05/13  1974/09/23  1992/12/18  1999/12/31

  5668-958 1.03.0  1988/09/13  1988/12/16  1997/06/30  1996/06/30
  5668-958 1.03.1  1989/09/19  1989/12/29  1997/06/30  1996/06/30
  5668-958 1.03.2  1990/09/05  1990/12/28  1997/06/30  1996/06/30
  5668-958 1.04.0  1992/09/15  1993/03/12  1997/06/30  2001/03/31

  5688-197 1.01.0  1991/09/11  1991/12/20  2000/09/06  1997/09/30
  5688-197 1.02.0  1995/10/24  1995/10/27  2000/09/06  2001/12/31

  5648-A25 2.01.0  1997/05/06  1997/05/23  2000/09/29  2004/12/31
  5648-A25 2.02.0  2000/09/26  2000/09/29  2002/12/31  2004/12/31

  5655-G53 3.01.0  2001/11/27  2001/11/30  2002/09/27  2004/04/04
  5655-G53 3.02.0  2002/08/20  2002/09/27  2004/02/27  2005/10/03
  5655-G53 3.03.0  2004/02/17  2004/02/27  2005/07/01  2007/04/30
  5655-G53 3.04.0  2005/06/21  2005/07/01  2008/09/29  2015/04/30

  5655-S71 4.01.0  2007/12/11  2007/12/14  2009/08/25  2014/04/30
  5655-S71 4.02.0  2009/08/25  2009/08/28  2018/03/12  2021/09/30

  5655-W32 05.01.00 2013/04/23 2013/06/21  2015/01/14  2020/04/30
  5655-W32 05.02.00 2015/01/14 2015/02/27  2017/09/11  2020/04/30

  5655-EC6 06.01.00 2016/02/16 2016/03/18  2020/03/09  -
  5655-EC6 06.02.00 2017/07/17 2017/09/08  2020/03/09  -
  5655-EC6 06.03.00 2019/09/03 2019/09/06  -   -

Cheers,
TomR  >> COBOL is the Language of the Future! <<

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



Tom,
Thank you for the table.
Actually I found some table in COBOL Migration Guide manual
https://www.ibm.com/support/knowledgecenter/hu/SS6SG3_6.3.0/migrate/igympreab2.html 


but your table is more detailed - I mean dates.
To make things more complex your table lack of third dimension ;-) I 
mean MLC vs VUE flavours, which is technically irrelevant, but introduce 
new PIDs (program numbers).
And this is good you preserved version numbering - that simplifies 
identification.


Funny fact: I vaguely remember 1999 and some official announcements 
about OS/VS COBOL withdrawals which were obscure and incomprehensible 
for me at the time. ;-)


BTW: This is pure curiosity, however was there any COBOL life on earth 
before 1974? I'm sure it was some COBOL, but it was really looong time 
ago. Maybe different product packaging and numbering, etc.


Regards
--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

Re: CICS COBOL co-compiler licensing?

2021-01-04 Thread R.S.


W dniu 30.12.2020 o 22:14, Charles Mills pisze:

1. Yes. That is what would be licensed, the necessary libraries.
2. Really? You never heard of a compile sandbox?
I can imagine compiler on other machine, but I cannot imagine software 
development for CICS with no CICS environment.
And I consider "compiler sandbox" as cumbersome. Yes, I heard about 
licencing.




3. That is more or less what I am asking about -- what are the license
options. "I'll just use R.S.'s machine" is probably not the answer I need.
I'm sorry for your dissappointment. However, please read all the 
subpoints I wrote. There are 5 of them, and only one is disappointing.

 .




--
Radoslaw Skorupka
Lodz, Poland








Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of R.S.
Sent: Wednesday, December 30, 2020 10:30 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: CICS COBOL co-compiler licensing?

W dniu 30.12.2020 o 18:46, Charles Mills pisze:

Does anyone know if there is an IBM license that covers the CICS COBOL
co-compiler short of a full-blown CICS TS license?

In other words, could you license the co-compiler for a "development
machine" without having to license the full CICS transaction server?

Few remarks
1. I may be wrong, but isn't it required to have some CICS libraries for
compilation?
2. Despite the above - I cannot imagine real programmer work without
runtime environment. So, coding a program for CICS environment without
the CICS itself is like coding z/OS program with no access to z/OS.
3. For real case there are some cost-effective options for program
development:
a) special licensing (several options) for regular machine
b) ADCD
c) Hercules ^H^H! zPDT with ADCD (that means your PC plus USB dongle
plus z/OS with IBM products suite)
d) remote access to remote machine on IBM premises (isn't it cloud? ;-) )
e) ask your colleague with access to the machine. I'm not sure about
legal issues, but I think I can allow my colleague to use my laptop and
MS Word. IMHO the same apply to use my laptop with my compiler. Why not
use "my" mainframe? I'm curious about it.





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: Using symbolic DD names

2020-12-30 Thread R.S.


W dniu 30.12.2020 o 20:21, Billy Ashton pisze:
Hey folks! I have a vendor product program that looks for different 
DDnames depending on the control statements passed into the program. 
Is there any way to define a dynamic DD statement using JCL symbols? 
For example, I would love to have //TB to correspond to 
TB01DAT, TB14DAT, or TB67DAT if I use SET TNO=01 or 14 or 67.


Is such a thing possible? I tried using an instream proc definition 
and INCLUDE MEMBER= that proc name, but that failed, and of course, I 
tried the straight up JCL as above, and it failed.


What do you all think?


It is impossible.

However similar things can be done using batch scheduler features.
For ControlM there are JSL and %%variables.
It is more or less as automated editor which produce JCL text just 
before it is submitted. All the %%variables have to be substituted at 
this time giving syntactically valid JCL, however some of %%var 
operations (like %%V1=%%ODATE-3) can be left in comment fields.

Other schedulers have similar facilities.

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: CICS COBOL co-compiler licensing?

2020-12-30 Thread R.S.


W dniu 30.12.2020 o 18:46, Charles Mills pisze:

Does anyone know if there is an IBM license that covers the CICS COBOL
co-compiler short of a full-blown CICS TS license?

In other words, could you license the co-compiler for a "development
machine" without having to license the full CICS transaction server?


Few remarks
1. I may be wrong, but isn't it required to have some CICS libraries for 
compilation?
2. Despite the above - I cannot imagine real programmer work without 
runtime environment. So, coding a program for CICS environment without 
the CICS itself is like coding z/OS program with no access to z/OS.
3. For real case there are some cost-effective options for program 
development:

a) special licensing (several options) for regular machine
b) ADCD
c) Hercules ^H^H! zPDT with ADCD (that means your PC plus USB dongle 
plus z/OS with IBM products suite)

d) remote access to remote machine on IBM premises (isn't it cloud? ;-) )
e) ask your colleague with access to the machine. I'm not sure about 
legal issues, but I think I can allow my colleague to use my laptop and 
MS Word. IMHO the same apply to use my laptop with my compiler. Why not 
use "my" mainframe? I'm curious about it.



--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: Scheduler (was: JCL divergence)

2020-12-30 Thread R.S.


W dniu 30.12.2020 o 15:17, Paul Gilmartin pisze:

On Wed, 30 Dec 2020 11:22:42 +0100, Stefan Skoglund wrote:

UNIX had early on cron which runs specific jobs regularly at
predetermined times while at (atd) is more like a one of JCL batch job.
...
LINUX has the same functionality.


Of course.  "... not far from the tree."

A shortcoming of cron we encountered is that there's no provision
to specify a timezone when scheduling a recurring event.

Do other schedulers have such a facility?

This is a particular irritatant for mobile device users.


Well, many moons ago we noticed that quite famous scheduler abends 
during time change (AFAIK only backward) - I mean DST drill.
However I guess it manage timezones properly. Of course mainframe is not 
typical mobile device so the problem with travelling mainframes in the 
pocket may be still not addressed.


--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: EBCDIC-ASCII converter and other tools

2020-12-29 Thread R.S.


Yes, exactly.
This is one of the reasons for custom-defined table.
Custom-defined is not "standard"
And yes, the goal is to change selected characters, and prepare the 
opposite table. Of course translation can be reversible when the table 
has unique values (this is first of the conditions) . So, for example it 
can be A->B translation, but B has to be translated as well, let's say 
B->A. That would change ADAM BROWN to BDBM AROWN (assuming other 
characters are not translated), but it reversible.
Let's say translation A -> B and B unchanged would give BDBM BROWN and 
there is no way to find out which character need to be reversed.



BTW: I feel guilty a little bit. I just asked simple question and paid 
attention of many gentlemen here. I hope the attention is not just to 
solve my boring, rather off-topic issue, rather there is nothing 
interesting to do instead. ;-)


However thank you all for your help!

--
Radoslaw Skorupka
Lodz, Poland







W dniu 29.12.2020 o 21:55, Charles Mills pisze:

I suspect the OP meant "ASCII" in the common (but granted pedantically
incorrect) sense of "one or more of the various code pages that use X'20'
for space, X'41' for A, X'30' for zero, and so forth, or a variant thereof."
Given that meaning, round trip is eminently possible.

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Seymour J Metz
Sent: Tuesday, December 29, 2020 12:32 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: EBCDIC-ASCII converter and other tools

Round trip is not possible with ASCII.

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







==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: EBCDIC-ASCII converter and other tools

2020-12-29 Thread R.S.

Yes, only text fields need to be translated just to be readable. And 
only few files would need to be translated back to original format.
So, no CF/LF issues, no RECFM issues, no packed decimal issues, no 
binary issues, etc.
Simple byte by byte conversion, which can be also reversed using 
"reversed" table.
In fact, the first thing that came to my mind was DFSORT, because I did 
some partial conversion of selected byte values.

The second was my tiny Turbo Pascal tool which I forgot and maybe lost.

--
Radoslaw Skorupka
Lodz, Poland






W dniu 29.12.2020 o 20:51, Charles Mills pisze:

If the input file contains not only text, but also binary and maybe decimal 
packed fields, you need an external description of the record format,

I think he has "round trip" translation in mind. Non-printable fields end up as hash 
in the ASCII file, but get restored properly on re-translation to EBCDI"C.

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Bernd Oppolzer
Sent: Tuesday, December 29, 2020 11:36 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: EBCDIC-ASCII converter and other tools

If the input file contains not only text, but also binary and maybe
decimal packed fields,
you need an external description of the record format, which can be
interpreted by the conversion program
(if the program should be able to work with all file formats and not be
specific for a certain format).

Characters - must be decoded (EBCDIC to ASCII)

Binaries - must be converted (big endian - little endian, to be useful
on Windows etc.) or converted to readable format (character)

Decimal - does not exist on Windows, that is, it must be converted to
character (readable format);
if you do this, the field offsets will change. This means, that you need
two descriptions (original and edited form)

Hopefully the record lengths and offsets are fixed; no variable length
fields ...

I once wrote such a program for a customer of mine, in C, and I believe
there was a open source tool,
which I used as first start. But I didn't search it myself; my customer
gave it to me. But it didn't do the job;
I had to invest some hours (or days). It was written in ANSI C.

OTOH: if the program only must handle one certain record format,
a very simple Pascal program with a fixed record layout would do.

Kind regards

Bernd



Am 29.12.2020 um 20:01 schrieb R.S.:

The input file contain some text and some other fields. CR/LF,
RECFM=FB/VB and other "end of line" issues are not relevant.
The idea is to convert it to readable format, analyze content and
maybe modify very few words or characters. Modified file should be
converted back to original format. Obviously conversion forward and
backward should give file equal to the source file.
Modification can be understood like replacement "Radek" to "Gil.." or
"" to "". No change of length, just byte to byte replacement.
ISPF browse/edit with proper codepage is not an option due to some
reasons I don't want to describe, technically irrelevant.
FTP translation is also not an option. And I would like to avoid Rube
Goldberg process like ftp put with no translation and then get with
custom translation. However this method can be run in batch and it is
feasible even for large files.
No, I'm not writing any tool - I want to avoid it and simply save
people's time spent on the process.
Maybe I'm naive, but I believed such tools simply exist and are
available for download - like many, many other small and useful
utilities.

Regards





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

- let us know by replying to this e-mail (thank you!),
- delete this message

Re: EBCDIC-ASCII converter and other tools

2020-12-29 Thread R.S.


W dniu 29.12.2020 o 18:54, Paul Gilmartin pisze:

On Tue, 29 Dec 2020 18:12:06 +0100, R.S. wrote:


1. Yes, maybe I described it incorretly.
Regarding your question - yes I need something like
convert ifile ofile [-tablefile]
Just byte to byte translation. No CR/LF issues, no record boundaries,
just byte to byte. The file can be large (may not fit in memory).


I'm surprised.  Is the input file a text file?  How are records delimited?
(Is it organized in records?)  If it's binary data I wouldn't expect
conversion to be useful.

Perhaps the answer to all such questions is RECFM=FB.

Does it originate on z?  How does it get to Windows?
FTP BINARY?

Are you writing a tool for non-programmers to use?


The input file contain some text and some other fields. CR/LF, 
RECFM=FB/VB and other "end of line" issues are not relevant.
The idea is to convert it to readable format, analyze content and maybe 
modify very few words or characters. Modified file should be converted 
back to original format. Obviously conversion forward and backward 
should give file equal to the source file.
Modification can be understood like replacement "Radek" to "Gil.." or 
"" to "". No change of length, just byte to byte replacement.
ISPF browse/edit with proper codepage is not an option due to some 
reasons I don't want to describe, technically irrelevant.
FTP translation is also not an option. And I would like to avoid Rube 
Goldberg process like ftp put with no translation and then get with 
custom translation. However this method can be run in batch and it is 
feasible even for large files.
No, I'm not writing any tool - I want to avoid it and simply save 
people's time spent on the process.
Maybe I'm naive, but I believed such tools simply exist and are 
available for download - like many, many other small and useful utilities.


Regards
--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: EBCDIC-ASCII converter and other tools

2020-12-29 Thread R.S.


1. Yes, maybe I described it incorretly.
Regarding your question - yes I need something like
convert ifile ofile [-tablefile]
Just byte to byte translation. No CR/LF issues, no record boundaries, 
just byte to byte. The file can be large (may not fit in memory).


I agree, it is not black magic. Actually ...I did it in the past.
I wrote simple program in Turbo Pascal. AFAIR 1 hour later I modified it 
to read translation table from a file.
However it was many moons ago and the tool is no longer usable, cause it 
is 16-bit application (for DOS) and current x64 Windows does not run 
such programs. There are tools like virtual machine or just DosBox, but 
it seems to be Rube Goldberg solution.
While I am still able to code a program (I hope so!), I don't want to 
start the project, install huge tool like Visual Studio, start learning 
"foreign" language, learn all the environment specifics, etc. It is just 
like building brewery just to have a beer for dinner. Not to mention 
security policies.
As I said, I did it in the past, using ancient (now) tools, and I know 
how to do it in z/OS realm. And it seems simple, so I hope someone 
already did it and the tool is available as many, many other tools.
HxD has many advantages, but I guess it has no batch mode. Batch is 
better - it is automatic ;-)
I don't know how many files will be processed that way, now it is 
possible to do it manually, but thing may change.


2. This is even simpler tool, maybe it address rare need - just to 
truncate first nnn bytes from beginning of file

Possible usage:
truncfile -header -12384 ifile ofile
truncates/deletes header, which is 12384 bytes long, the output is 
written to ofile. Ofile is shorter than ifile, the difference is 12384 
bytes. No CR/LF issues, just byte after byte.


I'm going to install HxD and try its features. However I'm still looking 
for something batch-able.


Thank you!

Regards
--
Radoslaw Skorupka
Lodz, Poland






W dniu 29.12.2020 o 17:32, Charles Mills pisze:

1. Conversion tool: your question is a little under-specified. You want a
file to file conversion program? Read in a file in EBCDIC and write it out
in ASCII?

Do you have any ability at all to write a program for Windows? In C, Rexx,
Visual Basic, etc.? The basics of translation are fairly simple. Would not
be terribly hard to read-in the translation table from some specified
source. Can you code at all in any non-mainframe-specific language? MS
Visual Studio is free in lightweight versions and would let you build and
debug a simple program pretty readily.

There is the nasty problem of line endings. (Don't get @Gil started ) Do
you expect "records" in ASCII? How will they be delimited? How will the line
endings in the EBCDIC file be indicated?

2. Pretty much the same answer.

@Steve, I don't think it's what he is looking for, but another vote here for
HxD in general. I find it useful for examining EBCDIC files on a PC.

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of R.S.
Sent: Tuesday, December 29, 2020 5:30 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: EBCDIC-ASCII converter and other tools

1. I'm looking for some simple tool for conversion EBCDIC to ASCII and
vice versa.
Unfortunately it has to run under Windows.
Requirements:
Run under Windows, preferrably in batch mode (command line interface)
Custom-defined tables of conversion

2. I'm looking for a tool similar to IDCAMS SKIP/COUNT - the goal is to
skip first nnn bytes of the file or skip file remainder.

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





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angie

Re: EBCDIC-ASCII converter and other tools

2020-12-29 Thread R.S.


Well...
Ultraedit offer some conversions, but no custom-defined tables. I need 
to use my own table - that's the problem.
For regular "quick and dirty" EBCDIC -> ASCII conversion I would use 
...MS Word, which has ability to read EBCDIC text files.

However it's also not the goal.
And important: I would avoid editors, especially those which read all 
file into memory - this is not good for larger files, which I expect to 
manage. I think HxD is better since it can edit large files without 
reading all the content into memory.


Gentlemen, thank you for your prompt response, I appreciate it.

Regards
--
Radoslaw Skorupka
Lodz, Poland






W dniu 29.12.2020 o 15:24, Steve Horein pisze:

I know several people that use UltraEdit:
https://www.ultraedit.com/wiki/Converting_file_encoding

I personally use notepad++, so cannot provide any first hand experience.

On Tue, Dec 29, 2020 at 7:30 AM R.S.  wrote:


1. I'm looking for some simple tool for conversion EBCDIC to ASCII and
vice versa.
Unfortunately it has to run under Windows.
Requirements:
Run under Windows, preferrably in batch mode (command line interface)
Custom-defined tables of conversion

2. I'm looking for a tool similar to IDCAMS SKIP/COUNT - the goal is to
skip first nnn bytes of the file or skip file remainder.


Any clue?

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: EBCDIC-ASCII converter and other tools

2020-12-29 Thread R.S.


W dniu 29.12.2020 o 15:20, Lennie Dymoke-Bradshaw pisze:

For the first requirement I was going to recommend SVC 103 but maybe that 
doesn't run under windows.

Where does the second utility have to run?


Windows also.
Yes, on z/OS side there would be not a problem - everything is available 
in the system.


I was looking for iebgener.exe, idcams.exe, iceman.exe, iconv.exe, etc. 
- no success ;-)

Fortunately I can use Minesweeper and Paint...

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

EBCDIC-ASCII converter and other tools

2020-12-29 Thread R.S.

1. I'm looking for some simple tool for conversion EBCDIC to ASCII and 
vice versa.

Unfortunately it has to run under Windows.
Requirements:
Run under Windows, preferrably in batch mode (command line interface)
Custom-defined tables of conversion

2. I'm looking for a tool similar to IDCAMS SKIP/COUNT - the goal is to 
skip first nnn bytes of the file or skip file remainder.



Any clue?

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: Installing RHEL 8.3 in Native LPAR

2020-12-28 Thread R.S.


W dniu 23.12.2020 o 03:41, Munif Sadek pisze:

I have been struggling to install RHEL 8.3 on a native HMC LPAR (Z14). My CPC 
is with multiple IFLs and I have configured couple of LPARs with Linux, 16 GB 
memory and with both Dedicated and non Dedicated IFLs but my Load from REMOTE 
MEDIA server to upload RHEL ISO (DVD image) hangs and times out after 55 
minutes, the LOAD function expire time.

my FTP *nix server is work fine as Load function can easily find genric.ins 
from the mounted ISO image but hangs after that. DVD image is 6.3 GB and hence 
can not create a DVD for a direct DVD load on HMC.

Has anyone installed RHEL 8.3 successfully on a Native LPAR (no z/VM or KVM) 
and willing to help.


I vaguely remember similar problem. It may or may not be the case, but...
Look at you ftp server log. What files are read and note the time. It 
may be network issue - first part of the installation process and the 
second part may use different ftp/network settings. While loading INS 
file was succesful, further step is not. Unfortunately I don't have my 
notes at the moment, so I cannot provide more detailed description.


BTW: Keep in mind z14 is the first machine which changed "Load from" 
behaviour - now all the communication with ftp server is being done by 
HMC. SE need not to be connected to the ftp server as it was required on 
z13 and older.


--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: JCL divergence

2020-12-28 Thread R.S.


W dniu 23.12.2020 o 00:35, John McKown pisze:

On Tue, Dec 22, 2020 at 5:26 PM Gibney, Dave  wrote:


WindowsJob...Huh


Right. I am so ignorant, perhaps the Windows (and Linux?) world doesn't
even have any unattended scheduled activities. I know that there is a
"Windows Scheduler" that can run a batch file (MSDOS .bat) automatically at
a given time or when a particular user does a "log on" (perhaps akin to a
TSO logon proc).

If the above is true (no automated unattended work), I wonder how companies
do {month,quarter,year}-end processing to generate reports to send to
appropriate governmental bodies. Or even, as in my employer, to
policyholders.


As other said, there are many batch schedulers available on Windows (and 
Linux). Some of them are well known mainframe product cousins like BMC 
ControlM, IBM TWS (former OPC), CA ESP. However there are other tools, 
which grew up on Windows platform and they have no z/OS version or this 
version is really poor. I warned you ;-)
However it is extremely important to understand there are big 
differences between JCL (z/OS) and Windows world. Yes, JCL (and z/OS and 
JES) is much, much better. And there are significant differences between 
z/OS and Windows based tool. Everything looks good when you schedule 
single step IEFBR14 job on one side and "echo Hello world" on the other 
side. But it is not usual production batch flow.


--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

Jesteśmy administratorem twoich danych osobowych, które podałeś w związku z 
prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które 
wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną 
działalnością bankową.
Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe znajdziesz w 
Pakietach RODO (w wersji polskiej i angielskiej), które są na www.mbank.pl/rodo


If you are not the addressee of this message:

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

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

We are the controller of your personal data, which you provided in connection 
with correspondence with us. We process your data for purposes resulting from 
the subject of correspondence, including those related to the banking services.
More information on how we protect and process personal data can be found in 
the GDPR Packages (in English and Polish), which are on www.mbank.pl/rodo.

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

Re: RMODE64

2020-12-21 Thread R.S.


Yes, it is.
However nowadays it seems to be harder than use RMODE31 and the need 
seems to be in far future.

Again: I'm not talking about AMODE.

BTW: I wish I would forget about 24-bit modes.

--
Radoslaw Skorupka
Lodz, Poland






W dniu 21.12.2020 o 17:07, Joe Monk pisze:

"Out of curiosity: why did you choose RMODE(64)?"

Hey man - its the way of the future!

Joe

On Mon, Dec 21, 2020 at 9:38 AM R.S.  wrote:


W dniu 21.12.2020 o 16:19, Ed Jaffe pisze:

On 12/21/2020 6:27 AM, Paul Gilmartin wrote:

On Sun, 20 Dec 2020 21:14:21 -0800, Ed Jaffe wrote:


There are many, Many, MANY restrictions!


Are these listed anywhere?  For code or for data?  Services calls?
Citation needed.


I was referring primarily to services. Our approach has been to invoke
those that don't support RMODE(64) from GLUE code running below the
bar. Many services still don't support AMODE(64). For those, even the
inout/output parameters must be below the bar.

(my humble question)
Out of curiosity: why did you choose RMODE(64)?
I understand AMODE(64) - more memory for data, but RMODE64 seems to me
good solutions for really large programs or maybe multi-program address
space like CICS.

--
Radoslaw Skorupka
Lodz, Poland



==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: Progam directory AD/Cycle C/370

2020-12-21 Thread R.S.


W dniu 21.12.2020 o 14:30, R.S. pisze:

Thank you for the information. I appreciate it.


BTW: Is there description/list of COBOL versions anywhere?
I mean z/OS family, something like
Enterprise COBOL 6.3  year
Enterprise COBOL 6.2  year
Enterprise COBOL 5.x  year
Enterprise COBOL 4.x  year
Enterprise COBOL 3.2 year
...
VS COBOL II ?
...
OS/VS COBOL ?



Auto-answer:
https://www.ibm.com/support/knowledgecenter/SS6SG3_6.3.0/migrate/igympreab2.html

However the list on the page above does not contain dates. It's a pity.



--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: RMODE64

2020-12-21 Thread R.S.


W dniu 21.12.2020 o 16:19, Ed Jaffe pisze:

On 12/21/2020 6:27 AM, Paul Gilmartin wrote:


On Sun, 20 Dec 2020 21:14:21 -0800, Ed Jaffe wrote:



There are many, Many, MANY restrictions!

Are these listed anywhere?  For code or for data?  Services calls?  
Citation needed.



I was referring primarily to services. Our approach has been to invoke 
those that don't support RMODE(64) from GLUE code running below the 
bar. Many services still don't support AMODE(64). For those, even the 
inout/output parameters must be below the bar.


(my humble question)
Out of curiosity: why did you choose RMODE(64)?
I understand AMODE(64) - more memory for data, but RMODE64 seems to me 
good solutions for really large programs or maybe multi-program address 
space like CICS.


--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

list of APPLIDs

2020-12-21 Thread R.S.


How to get list of available APPLIDs?
I mean
LOGON APPLID=applidname

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: Progam directory AD/Cycle C/370

2020-12-21 Thread R.S.

Thank you for the information. I appreciate it.

BTW: Is there description/list of COBOL versions anywhere?
I mean z/OS family, something like
Enterprise COBOL 6.3 year
Enterprise COBOL 6.2 year
Enterprise COBOL 5.x year
Enterprise COBOL 4.x year
Enterprise COBOL 3.2 year
...
VS COBOL II ?
...
OS/VS COBOL ?

--
Radoslaw Skorupka
Lodz, Poland

W dniu 21.12.2020 o 14:17, Joe Monk pisze:

"Just curious: What was "AD/Cycle"?"

AD/Cycle was part of SAA - the systems applications architecture. AD/Cycle
referred to the "Application Development Cycle".

https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?appname=skmwww=897%2FENUS290-529=AN=service%20initializer=ibmsearch_a=CA

Joe

On Mon, Dec 21, 2020 at 7:10 AM R.S. wrote:

W dniu 15.12.2020 o 10:19, Peter pisze:

Hello

Does anyone have a copy of Progam directory AD/Cycle C/370 1.2 ?

I don't find the installation manual over web might be due to

backlevelled

Any pointers ?

Just curious: What was "AD/Cycle"?
I'm aware the above can be found in old compiler names, but ...was is
brand name or some marketing name?

--
Radoslaw Skorupka
Lodz, Poland

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

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

If you are not the addressee of this message:

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

Re: Progam directory AD/Cycle C/370

2020-12-21 Thread R.S.


W dniu 15.12.2020 o 10:19, Peter pisze:

Hello

Does anyone have a copy of Progam directory AD/Cycle C/370 1.2 ?

I don't find the installation manual over web might be due to backlevelled

Any pointers ?


Just curious: What was "AD/Cycle"?
I'm aware the above can be found in old compiler names, but ...was is 
brand name or some marketing name?


--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

DB2 v12 and IAG2

2020-12-21 Thread R.S.

DB2 v12 introduced new Insert Algorithm 2 (IAG2), which was the topic of 
Red Alert and the recommendation was to disable it.

Question: is it fixed somehow or the recommendation is still valid?

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: Security and z/OS open source tools

2020-12-11 Thread R.S.

W dniu 09.12.2020 o 22:58, Frank Swarbrick pisze:

I have downloaded and installed in my personal z/OS Unix directory curl and a few other
z/OpenSource tools from Rocket Software. I have asked my z/OS security guy if we can go ahead and
have our systems group (outsourced to IBM zCloud) "officially" install them. He came
back with the following: "My question is how do we approve, track and secure the open source
code we are putting on z/OS?"

Does anyone have suggestions on answering this concern?

Timothy gave you good answer.

However I dare to share my comments:
1. It is NOT matter of open-source or closed source.
2. There is difference between freeware and open source. Freeware can be
closed source and open source can be licensed. And licensed is usually
paid, but it need not to be.
3. IMHO the most important is the support. It need not be contractual
(usually paid) formal support, but as with many other tools (Firefox,
java in the old years). CBT tools are not supported and usually the
update process is slow or none. However tools from one-man-band-company
are also "suspected" in terms of support.
4. Is the tool a part of airplane or just bicycle? In other words how
crucial for the production it is. Some tools are very useful, but lack
of them would not stop production. It would make things harder.
5. Security issues. Many "insecure products" provide no risk at all when
used in controlled, closed, isolated environment. It is important to
understand the vulnerabilities.

--
Radoslaw Skorupka
Lodz, Poland

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

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

If you are not the addressee of this message:

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

Re: does anyone recall any details about MVS/XA?

2020-12-11 Thread R.S.


W dniu 09.12.2020 o 20:02, Paul Gilmartin pisze:

On Wed, 9 Dec 2020 19:31:34 +0100, R.S. wrote:

...

I perceived aversion to RECEIVE FROMNTS as UNIXphobia.  Our product
was not so large that DASD space was a concern.  Can't please everyone.

Gil,
Don't kill messenger ;-)


Was that statement hostile?  (But smiley noted.)
And thanks.

Just a joke.
How do you call it? Lost in translation?
Seriously: it wasn't hostile.


Yes, it is possible to IPL from network, it has been possible since z990
or z9.
...
Of course the server is not included, so it is up to you to set up some
ftp/sftp/ftps server and disk space, and Internet connectivity.And power
supply...


And, especially, configure IP address and path in (HMC?) bootstrap loader.

How much driver system needs to be installed to support RECEIVE ORDER?
(Is that the next step?


Well, I'm not sure I understand it correctly, however installation 
process is the following:

z/OS
- prepare IOCDS (how? using assembler macros!) to make your 
configuration compatible with IODF delivered with Driver System.
- IPL from network. Note, it is NOT z/OS, it is standalone utility (dss) 
to restore three disk volume images.

- IPL Driving System from restored DASD.
- logon to z/OS Driving System and work as on regular z/OS - run 
ServerPac Installation Dialog.


z/VM
- IPL from network - this time some z/VM image will start.
- press ENTER, ENTER, ENTER... - like in Windows ;-)

z/Linux
similar to the above

z/VSE
I have no idea

z/TPF
I have no idea



... zLinux installation is IPL-able

>from network. ZZSA is IPL-able from network.
ZZSA?  AZERTY keyboard?


This is standalone utility from Jan Jaeger.
It may be last resort when you cannot IPL your z/OS due to syntax errors 
in PARMLIB or IPLPARM.



Regards
--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: does anyone recall any details about MVS/XA?

2020-12-09 Thread R.S.


W dniu 09.12.2020 o 19:14, Paul Gilmartin pisze:

On Wed, 9 Dec 2020 18:25:19 +0100, R.S.  wrote:

...
For blank new installations - download (or order media) DVD images of
Driver system and put it into DVD drive in HMC... Well... there is no
longer DVD drive... However you can put DVD content into some ftp server
directory and IPL from that directory.


Ah!  So it's possible to IPL from network.  (IANASysadmin, so not in my
skill set.)  FTP only, or other schemes?  FTP is problematic; too widely
considered insecure.  Windows has a server, concealed under IIS; I've
used FileZilla server.

MacOS and Linux readily support mounting .iso images; so "content" step may
be skipped.  Windows image mounter flickers in and out of support.  I used
Virtual CloneDrive (Dolly? in logo).

Never for IPL (IANASysadmin), but for SMP/E RECEIVE FROMNETWORK.
Testers found the process so tedious I fell back to packaging a "pax"ed
SMPNTS and recommending "pax -r"; RECEIVE FROMNTS.

Some customers wished for a set of .xmit PDSU.  I demurred; masochists:
Too many steps for them to install; unlike any IBM product (but the
customer cited one product so packaged.  It was from a recently-acquired
subsidiary).  And too many steps for me to package.

I perceived aversion to RECEIVE FROMNTS as UNIXphobia.  Our product
was not so large that DASD space was a concern.  Can't please everyone.


Gil,
Don't kill messenger ;-)
Yes, it is possible to IPL from network, it has been possible since z990 
or z9.
Nowadays it is possible to use FTP, SFTP or FTPS protocol. I talked to 
some IBMer responsible for internal code and they changed all "ftp" to 
use any of three protocols/flavours. It is already changed since z14.


Of course the server is not included, so it is up to you to set up some 
ftp/sftp/ftps server and disk space, and Internet connectivity.And power 
supply...


Regarding .ISO images - this is ISO, standard! Vanilla Win10 will manage 
it. Of course a lot of other tools also manage such images.
And no, ...yes! There is a choice: ISO file from Internet or physical 
DVD from IBM. Still no PDSU, XMIT, etc. Caution: DVD content need not to 
be set of MVS files. Note, z/VM is on DVD as well. There are standalone 
tools on DVD (or IPL-able from network). zLinux installation is IPL-able 
from network. ZZSA is IPL-able from network.


BTW: previously z/OS Driver was distributed on DVD, but it *HAD* to be 
physically ran from DVD. Otherwise you could IPL it, but next step 
wanted to read from DVD drive. FTP was not an option. At the time z/VM 
was installable/IPL-able from both DVD and network.


--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: Z15 zedc compression and CONNECT DIRECT, MFT compression

2020-12-09 Thread R.S.


W dniu 09.12.2020 o 18:52, Kenneth J. Kripke pisze:

Hello;

  We have upgraded from a Z14 to Z15 processor, and, have experienced
something curious regarding the SMF TYPE 30 section being generated for
Connect Direct as well as Tibco's MFT 8.0 file transfer products.

Both products are enabled to use ZEDC compression, but, when generating SAS
reports from SMF type 30 records, we  see   SMF30USO{Offset to zEDC usage
statistics Section} and the, SMF30USL{Length of zEDC usage statistics
Section}  containing data.

We do not see the SMF30USN{Number of zEDC usage statistics sections} having
data.  This has been noticed since upgrading from a z14 to a z15 processor.
Has anyone else seen anything like this in their environment running MFT 8.0
or Connect Direct ?


Kenneth,
Please note, the hardware for zEDC functionality is completely rebuilt 
between z14 and z15.
In z14 it was I/O card, in z15 it is part of CPU IC. From user point of 
view it is just faster engine, but inside it work different way.


Maybe this is the reason of changes in SMF records?

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: does anyone recall any details about MVS/XA?

2020-12-09 Thread R.S.


W dniu 09.12.2020 o 17:05, Farley, Peter x23353 pisze:

OTOH, quantum computing (or its successor(s)) may change the paradigm entirely 
and moot any 64 vs 128 bit issues because qubits are so different from bits.


Well...
I remember stories about IPv6 addressing. It is much more capacious than 
IPv4 and it will address current constraints and future needs.

However I heard about it 20 or 25 years ago. And I still use IPv4.

Regarding memory - pricing is very important here. Nowadays 16 GB or RAM 
is rather basic or even poor PC configuration. So, new application 
consume more and more memory without any reflection. Just because the 
memory is cheap and available.

So demand for memory will be growing rapidly. And it is growing now.
In other words typical simple Notepad - like application will be as dumb 
as yesterday but it will consume much more memory.

8 billion times? Well, stay calm and watch it...

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: does anyone recall any details about MVS/XA?

2020-12-09 Thread R.S.


W dniu 09.12.2020 o 02:41, Paul Gilmartin pisze:

On Wed, 9 Dec 2020 00:48:31 +, Seymour J Metz wrote:


You needed an MVS driver system to install MVS/XA. Most customers already had 
an existing MVS/SP system, and didn't need to order the starter system. IPO and 
PSO were available later. Optional souce was available on tape. There was no 
PTF optional source; if the module was hit by service, you had to rely on the 
microfiche.


What's the process today for a new site with no real tapes?


For users already having z/OS as driving system - just download 
ServerPac to HFS/ZFS and install it.
For blank new installations - download (or order media) DVD images of 
Driver system and put it into DVD drive in HMC... Well... there is no 
longer DVD drive... However you can put DVD content into some ftp server 
directory and IPL from that directory.


--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: Edit the OSA/ICC definitions using the HMC

2020-12-06 Thread R.S.


W dniu 04.12.2020 o 19:16, Tony Thigpen pisze:
We have never been able to use the edit function unless we were 
directly on the HMC. Using it remotely via the web produces the same 
results you are seeing.


I get around it by ftping the config to a small mini-ftp box then 
accessing the FTP box from my pc. I have to move the config back and 
forth to the HMC, but I get my job done. I also have to ftp the config 
back down so I can see the errors when I do something wrong.



This is old pain with appliances (HMC, SE, Brocade director...) and 
modern browsers. New and new updates disabled many previously working 
functions.
My trick for that is easy: simply have virtual machine with downlevel 
versions of browser, java, etc. IT Security will not like it, but it is 
really safe when the downlevel machine is solely used for managing few 
appliances and have limited rights and connectivity.
Of course the other way is to have the newest directors and HMCs and SEs 
...and mainframes. And additional physical HMC at home office.


My 0.02

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: Edit the OSA/ICC definitions using the HMC

2020-12-06 Thread R.S.


Do you mean HMC (HMA) reboot or just physical machine reboot?
According my understanding you can reboot HMC and it is independent from 
SE reboot since both are separate virtual objects (virtual machines). Of 
course reboot of physical machine affect all virtual objects/machines 
under.


BTW: I do not suggest to reboot SE with no purpose, however it is 
perfectly possible during normal operations. Temporary lack of SE will 
not disrupt production, but some administrative operations (IOCDS 
update, IODF activate, change LPAR weights) will be temporarily 
unavailable.


--
Radoslaw Skorupka
Lodz, Poland






W dniu 04.12.2020 o 22:37, Dana Mitchell pisze:

Thats my understanding too Tom.  According to our SSR,  its a pain if they have 
to reboot the HMC for whatever reason,  they have to make sure the SE is 
switched to the correct one so they don't reboot the Primary SE.
Dana

On Fri, 4 Dec 2020 13:15:52 -0800, Tom Brennan  
wrote:


And there's the new HMA Hardware Management Appliance on the z15 that
eliminates the need for external HMC boxes.  I haven't seen this yet,
but one rumor is that the existing 2 SE 1U boxes inside a mainframe
(which to me look exactly like rack mount HMC boxes anyway) will boot up
the HMC software first, then start a VM task which boots up the SE
software.





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: Is ISGENQ a bit pricey?

2020-11-27 Thread R.S.


W dniu 27.11.2020 o 14:35, Peter Relson pisze:

It seems reasonable that it would in a real sysplex.

This question and the original post make it sound like the poster's system
was not in a sysplex.
The display showed that it is in a sysplex. Is that not a "real sysplex"?


My understanding:
"real sysplex" - properly configured and tuned Parallel Sysplex with GRS 
STAR, etc.
"not real sysplex" - somehow configured sysplex or parallel sysplex with 
lack of resources, GRS ring. Maybe good for some development or 
functional tests, but from performance point of view...


Of course this is my interpretation of someone's words. Nothing more. I 
can be wrong.


--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: IEA213A DUPLICATE VOLUME

2020-11-21 Thread R.S.


Gil,
Please, pay attention to "human-operated". I did not use MTL 
intentionally, for the reasons described below.
ATL means Automated Tape Library. Sometimes people call it "robot". 
Sometimes it is VTS. Sometimes VTS don't have physical tapes at backend 
- so there is no physical robot.
ATL could also mean IBM tape library - important for system definitions. 
Other vendors do not make IBM-compatible ATLs and tend to use MTL 
definition - Manual Tape Library for their robots and VTLs/VTSes. This 
is because of system management.


However there are real MTLs and real installations with so called stand 
alone tapes - just bunch of drives operated by human operators. And tons 
of cartridges on shelves. Just like in the old times of open reels. In 
this case it is up to operator what tape will be mounted. ...and it is 
up to RMM (or other TMS) to be a supervisor. However it is perfectly 
possible to mount "this green cart with label LBL001, you know which 
one". And the green cart (actually green sticker) can be one of dozen 
carts labeled as LBL001. How to identify them? Very simple: one is 
green, the second is almost green, third is also green but there is 
marker sign "not this one", etc. etc.
Ridiculous? Well, my colleague used diskettes in that way. No, instead 
of stickers he used pencil and coffee stains to identify. Was it 
working? NO!


--
Radoslaw Skorupka
Lodz, Poland






W dniu 22.11.2020 o 03:57, Paul Gilmartin pisze:

On Sun, 22 Nov 2020 02:10:45 +0100, R.S. wrote:


IMHO it was the same error as nowadays: bad naming.
I didn't work with removable DASD, but I worked with physically
removable, human-operated tapes. And it was administrator responsibility
to have proper naming convention and unique volume serials. Exceptions
in justified scenarios only.


That uniqueness might have been enforced more automatically for tape
than for DASD because the tape volume serial might need to match the
numbered slot in the library.

The scenario justifying an exception might be for mass production of
products distributed to customers: the volser must match that in the
README.

I once had a conflict between the volser in our README and a DASD
volume.  Fortunately, ops was able to dismount that DASD logically
long enough for me to write a master tape to send to Manufacturing.

An organization (SHARE?) once tried to maintain a world-wide
registry of tape volser prefixes.  They rapidly exhausted the
name space.

UUID?

-- gil

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



==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: IEA213A DUPLICATE VOLUME

2020-11-21 Thread R.S.


IMHO it was the same error as nowadays: bad naming.
I didn't work with removable DASD, but I worked with physically 
removable, human-operated tapes. And it was administrator responsibility 
to have proper naming convention and unique volume serials. Exceptions 
in justified scenarios only.


Of course nowadays duplicated DASD volsers are usually (not always) 
result of volume cloning, which is a little bit different animal.


--
Radoslaw Skorupka
Lodz, Poland






W dniu 22.11.2020 o 00:33, Tony B. pisze:

Anyone else out there remember removable DASD, Pizza Ovens and 3340? Having
duplicate volsers was more prone to human error at the physical level.

On Sat, Nov 21, 2020 at 11:48 AM Jesse 1 Robinson 
wrote:


Your DASD managers are the culprits. As I said in another post, this
condition could persist for quite some time until an attempt to vary a
duplicate volser online or to IPL.

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

-Original Message-
From: IBM Mainframe Discussion List  On Behalf
Of Steve Lee
Sent: Friday, November 20, 2020 2:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: IEA213A DUPLICATE VOLUME

*** EXTERNAL EMAIL - Use caution when opening links or attachments ***

Hi Robinson,

Good to know the experience you were with.

Ops has a enough time to reply the WTORs in those particular lpars.

Those Volumes are 3400/3800/4800 strings, not all of volumes but some of
ranges.
I need to check with Storage if those has been CLIPped.
These messages started coming out from a few last IPL cycles, no messages
until the last few IPLs which I think Storage made a change before.

Possible solution would be that being allowed to indicate that in the case
of a dup, either the HIGHER or LOWER address be put offline in IO
Configuration part in IODF when a dup is encountered if the CLIPped is a
necessity at their end.






==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: Any separate ListServer for HCD & HMC

2020-11-20 Thread R.S.

> Q: 
> is it non-disruptive or disruptive when massaging the Weight & number of 
> Processors if do as follows? 

In general it is non-disruptive. However big change, let's say from 75% to 5% 
can be very troublesome. 


- the Weight value: from HMC(2.14.1)>click on a CEC level>Operational 
Customization>Change LPAR Controls, then update the Weight, 
   then click on "Change Running System" button, and let it take immediate 
effective?
   or, click on "Save and Change" button, does this take immediate effective as 
well without any disruptive?
   Note: this is to be done for a regular zOS lpar

Save and change make it effective and it will be saved for the future. What 
future? POR. 


- the number of Processors: Note: this is to be done for a CF lpar
from the HMC Operating System Message in CF lpar, issue D CPS and make sure 
of the Processors status, 
issue CP xx OFFLINE, then D CPS again to make sure of it taken offline,
from same path explained in first paragraph above, update the number of 
Processors (this is Shared, not Dedicated in this case)
then click on "Change Running System" button, and let it take immediate 
effective?
Note: this is a Shared Processor, thus other Lpars in this CEC will take 
the advantage of Processors utilization as much as one processor 
released from the CF lpar?  and this must be non-disruptive right? No need 
to move the Structures, and re-allocate them?

I admit, I don't understand the scenario. Maybe it is result of my poor 
English, or maybe you can decribe it in simpler words. 
Few remarks:
CF love dedicated engines! So any shared engine is good for non-prod 
environment and even then people say it is not good idea. Note: things changed 
recently, but I don't want to describe details, because my memory is failing in 
this area. 
In many cases single ICF is enough. 
When changing CPU power, think about whole dedicated ICFs, not weights.
AFAIR for share ICF you can change the weights as usual. However last time I 
did it 7 or 8 years ago.
Console commands (CF interface) regarding CPUs are non-disruptive (I believe 
so), however change (remove) from SE is disruptive, unless things were changed. 
In properly configured syplex you should have at least two CFs (no single point 
of failure), so your mistake should trigger structure rebuild. It is not 
something people like, but it is like failover procedure. 
In case of doubt just do it first on sandbox sysplex. 

- any others that I might miss at this moment?
Yes, but it depends on your needs and your setup. 
For example, when you watch CPU weight change you will notice separate tabs for 
GP (regular CP), zIIP, IFL, former zAAP. The tabs exist only if you have that 
kind of processor. 
It is general rule for HMC - you won't see things that are not enabled. 
Sometimes enablement means configuration, and sometimes that means orderable 
(usually paid) feature. And it depends on user authorities - SERVICE see other 
things than SYSPROG. And PEMODE see a lot more. 

HTH

--
Radosław Skorupka

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

Re: QSAM VB update in place

2020-11-20 Thread R.S.


W dniu 20.11.2020 o 18:01, Paul Gilmartin pisze:

On Fri, 20 Nov 2020 16:47:58 +, Seymour J Metz wrote:


However what If I would like to make the record size larger I might get a s0c4 
possibly

QSAM doesn't allow changing the record length and BSAM doesn't allow changing 
the block size


What about RECFM=VBS, initially padding each block with a null segment,
allowing limited insertion, expansion, and deletion?

Can a VBS block consist entirely of a null segment?
"Aint no rule saying a dog can't play basketball!"

OK, who's using VBS? Of course except IFASMFDP.
I don't say it is impossible, I say it is rarely used.



As others have written, this is a use case for VSAM.

?
Isn't that cheating?  ESDS?  KSDS?  RRDS?  ...?


No, it isn't. VRRDS is the choice for such scenario.
Of course Db2 table is better.

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: Why does SDSF ST only show current JESPLEX jobs?

2020-11-20 Thread R.S.


W dniu 20.11.2020 o 20:19, Farley, Peter x23353 pisze:

A colleague asked me today if there was an error in SDSF because from his ISPF 
/ SDSF DA screen he can see all active jobs with selected names (e.g., using 
PREFIX or a SELECT command) across the entire SYSPLEX.

However, using his ISPF / SDSF ST screen he can only see those selected job 
names which are running in the JESPLEX to which he is logged on.  We have two 
JESPLEX instances with different LPAR's in each one.

I confirmed the behavior he reported.  My ISPF / SDSF ST screen behaves the 
same as his, and my ISPF / SDSF DA screen does too.

At this point I am just curious, is this WAD or an SDSF bug?

TIA for any info or RTFM you can provide.


So, you have multiple JESplexes within SYSPLEX?

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: Any separate ListServer for HCD & HMC

2020-11-20 Thread R.S.


W dniu 20.11.2020 o 19:00, Steve Lee pisze:

Hi,

Is there a separate ListSever for the IO Configuration(and HMC tool included) 
as an example of RACF-L server?
Or IBM-MAIN has been covered these items?


This is proper list.
What problems do you have?
We will try to help.

(proud author of HCD and HMC courses)

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: IEA213A DUPLICATE VOLUME

2020-11-20 Thread R.S.


W dniu 20.11.2020 o 03:08, Steve Lee pisze:

Dear,

These messages come out at the time of IPL in past few IPL cycle;

IEA213A DUPLICATE VOLUME 'RP@C03' FOUND ON DEVICES 3404 AND 4802.
IEA213A REPLY DEVICE NUMBER WHICH IS TO REMAIN OFFLINE
IEA213A DUPLICATE VOLUME 'RP@C04' FOUND ON DEVICES 3405 AND 4803.
IEA213A REPLY DEVICE NUMBER WHICH IS TO REMAIN OFFLINE
IEA213A DUPLICATE VOLUME 'RP@C05' FOUND ON DEVICES 3406 AND 4804.
IEA213A REPLY DEVICE NUMBER WHICH IS TO REMAIN OFFLINE
~
~



My Research:

When systems starts initialization after loading it makes some set of volumes 
needs to be offline due to saem volume label.
(In IODF part, all volumes listed above are "Offline=No")
Some of the volumes on these system has duplicate volume labels defined to 
them, While making these volume offline system gets confused and generates 
these WTORs to ask the operator which one to make offline when it finds two 
volumes has same volume label.

There has not been changes to IODF. Storage team can give more clarification 
about these volumes gets assigned with duplicate volume labels.
But they are also confused why it happens.


Any input will greatly be appreciated.



Short explanation:
During IPL z/OS scan all the volumes defined as ONLINE. Duplicates are 
not allowed, so operator has to decide which one to KILL (vary offline). 
Of course at the time there are no ISPF or other means to easily check 
wich one is "better" or rather which one should be used. Note: duplicate 
volser could mean just another volume with completely unrelated content, 
but likely it is a copy of the volume with same name. In this case it is 
very hard to find out which is copy, which is original and which volume 
to use. Ask author of the copy!
Note: volumes are defined as available and further available volumes are 
defined as ONLINE in OS Config part of IODF. And this is solution to 
separate "primary" set of volumes and the clone set. OS Config PRIM will 
make cloned addresses as unavailable or just OFFLINE. OS Config CLONE 
will make primary volumes unavailable, but cloned volumes as ONLINE. And 
voila - simple Flashcopy (Shadowimage, TF/Clone...) and you have clone 
of your system and the clone can be IPLed with few changes in LOADxx 
member.
Note2: A person who makes volume copies should be aware of OS Config 
settings and generally should avoid scenarios like yours. It just 
mistake made by the person.


--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: Is there a JES2 command to submit a job?

2020-11-19 Thread R.S.


W dniu 19.11.2020 o 22:13, David Spiegel pisze:

Hi Radek,
After I sent it, I realized that I addressed you incorrectly. Sorry.


No problem at all. I just suspected there is some meaning of such 
sentence which I don't understand. Curiosity - that's all.


Regards
--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: Is there a JES2 command to submit a job?

2020-11-19 Thread R.S.


W dniu 19.11.2020 o 21:46, Wayne Bickerdike pisze:

Charles,

I like Bobby Herring's solution. We use similar commands combined with
automation at one customer.

AUTO is very, very easy to install.

It uses a PDS with this syntax : @2230

At 2230, it does whatever is in the member with a day flag:

+1+2+
*  MTWTF   I SMF
MTWTFSS S DELDUMP
I clean up the dump dataset at intervals.


Maybe I lost some posts, but I haven't seen any mention of the tool.
Is it something available on CBTtape?

I guess there may be other tools on cbttape as well. This is another 
point to mention, which I omitted for simplicity.
Yes, there is big gap between answer to help person and to describe all 
possible solutions.


--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: Is there a JES2 command to submit a job?

2020-11-19 Thread R.S.


W dniu 19.11.2020 o 21:48, David Spiegel pisze:

Hi Skip,
"... That means your job may contain DD * statements, etc.  ..."
As of z/OS 1.13, Cataloged Procedures can have DD *


Yes, I wanted to say that as well, but simply forgot. There are also new 
features in JCL since z/OS 2.1, which I didn't mention. However my point 
was to focus on started job - which is very, very close to the topic. 
And it is really simple, isn't it?



BTW: "Hi Skip" - is it some kind of idiom?



--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: Is there a JES2 command to submit a job?

2020-11-19 Thread R.S.


W dniu 19.11.2020 o 00:00, Charles Mills pisze:

Is there a JES2 command to submit a job from a PDS or PROCLIB, roughly
analogous to TSO SUBMIT?

I want to run a predefined job, unmodified, once a day. (No, I don't have a
real scheduler.) I figured I could do something with $T A,I=86400,'command'
but I don't see what the command would be. It seems like an obvious thing
for JES2 to be able to do.

Do I use $VS,'S proc' and run it like a started task that just happens to
end after a minute or so?

I vaguely recall there is a way to submit a job (via TSO or whatever) such
that it gets held and then could be released with a JES2 command but also
left in the input queue for another release? Am I on the right track? Or ...
?

Thanks. Sorry for the newbie question. I'm a newbie operator.


My €0.02:
1. For professional scheduling there are commercial tools like BMC CTM, 
IBM TWS, CA ESP, etc. Of course it is not worth to pay just to schedule 
one job a day. However ...maybe you have it already in your shop? Just 
check it.



2. For JES2 (and no batch scheduler) I would use $TA... $VS S member.
That means your JES2 'wannabe-scheduler'  periodically issue START 
command, which is MVS command.
Old farts say it is for starting members of PROCLIB, that mean JCL 
procedures. It is no longer true (for years), you can start a job using 
same command and same library. That means your job may contain DD * 
statements, etc.

Not enough? Well you started job/procedure may submit regular job.

Caution: is it SIMPLE. Mainframe gurus will hate it ;-)


3. There are other ways to skin a cat. Some of them include existing 
tools, like cron, however really aspiring way is to start with 
assembler, APF and MODESET 0. ;-)

(yes, this is kind of joke)

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: Improve OMVS cp performance?

2020-11-17 Thread R.S.


W dniu 17.11.2020 o 01:57, Wayne Bickerdike pisze:

Atlas rang a bell and then I remembered it was used at the Rutherford labs
in Chilton.

I worked at AERE (Atomic Energy Research Establishment) which was next
door. They were basically the same campus but AERE was secure and
Rutherford wasn't.


[...]

Chilton!
Huge set of old pictures!
And rare gem: picture of 2305 DASD.

Also some pictures of Atlas parts, S/360, first Cray, ICL machines, etc.

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: Finding JES2 node name

2020-11-17 Thread R.S.


W dniu 17.11.2020 o 16:53, Tim Hare pisze:

I have some code that follows a control block chain to the HCCT to get the JES2 
node name, but that requires going to key zero (or so the source says, it's 
been years ).  Is there a way to retrieve the JES2 node name in a  program 
running in batch, without being APF-authorized? We'd like to remove the need 
for this program to be in an APF-authorized library.


Yes, it is possible, even without assembler programming.
See Mark Zelden's IPLINFO, which is REXX code.

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: Sequence or procedure of getting new dasd

2020-11-17 Thread R.S.


W dniu 17.11.2020 o 05:15, Peter pisze:

Hello,

I am just trying to understand on how new pool of volume is created in DS8K
box , then what values are shared from DS8K with zOS system programmer to
the newly created LCU in IODF ?

Does the newly added DASD UCB needs a POR or just soft activation of IODF
holds good or we need a IPL ?

Any advise are much appreciated


There are two parts of the excercise:
1. DS8K configuration.
2. System part.

CAUTION: NEITHER IPL NOR POR IS REQUIRED. THIS IS MAINFRAME!

First part belongs to hardware engineer. It can be IBM CE or your 
colleague. Note: some DASD boxes cannot be configured by user depending 
of vendor approach.

In this part CE configure CUs, number of base devices and aliases.
Output: CUADD (Logical CU number), UA scope for 3390B and UA scope for 
aliases (usually the remain of 256)

To simplify I assume there are no tricks with CU to channel assignments.

Second part is system administrator work.
You get list of CUs with the number of 3390B's and 3390A's.
You define it in IODF using HCD.
Then ACTIVATE.
Voila - you have new devices in your system. With no outage.

Then VARY dev ONLINE
Then ICKDSF
Then VVDS
Then DFSMS storage groups.


HTH



BTW: I cannot remain *any* IPL of POR when added new DASD box to the 
system. Even I/O cards can be added dynamically.

Of course this is my limited 20 years experience in few shops.
Tapes are completely different... that means no IPL as well ;-)

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: Improve OMVS cp performance?

2020-11-16 Thread R.S.


As a old computer hobbyist I've collected (very) few pictures of TR 4.
Wooden parts of cabinets, construction similar to contemporary 19" racks.
Nice machine, part of IT history.

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: Can a non-admin restrict others from viewing one of their own MVS data sets?

2020-11-13 Thread R.S.


W dniu 12.11.2020 o 14:33, Seymour J Metz pisze:

There's nothing special about TSO; HLQ=userid is handled the same way in batch, 
STC and TSO.


Yes, that's correct. My mistake.
Corrected version below.

Few points:

1. In MVS world there is no concept of file ownership like in Unix.
2. HLQ=userID is special case, but it is rather "ALTER by
default", which is hard to restrict and it has very little to do with
authorities management.
2.1 Such datasets are called "his own" despite there is no ownership
concept.
2.2 (deleted)
2.3 (added) Note: special treatment works only if the profile exists. In 
other words, non-protected datasets (no profile covers them) are not 
allowed "ALTER by default". However the scenario may be even more 
complex when Global Access Table is used.

3. Every user may or may NOT have rights to manage dataset
authorities, his own (HLQ=userid) OR OTHER DATASETS.
4. Details depend on your setup. Usually "his own" datasets are in scope
of the user (userid is the owner of userid.** profile) and that is
enough to manage access list and UACC.
5. However admin may restrict RACF commands like AD, ALDSD nad PE and
then user cannot use them to manage rights. There are other methods also.

HTH


BTW: Security for datasets is considered as the most basic part of RACF 
and usually this is part of basic RACF courses. However in details it is 
very complex IMHO.


--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: Can a non-admin restrict others from viewing one of their own MVS data sets?

2020-11-12 Thread R.S.


W dniu 06.11.2020 o 22:43, Frank Swarbrick pisze:

In the Unix world one can use chmod (change mode) on their own files to make it 
so non-superusers cannot view a particular file.  Is there anything similar for 
MVS data sets?


Few points:
1. In MVS world there is no concept of file ownership like in Unix.
2. For TSO users HLQ=userID is special case, but it is rather "ALTER by 
default", which is hard to restrict and it has very little to do with 
authorities management.
2.1 Such datasets are called "his own" despite there is no ownership 
concept.
2.2 Note, special treatment is not for every RACF user, it is for TSO 
users only. So, for example ftp and many other methods are excluded 
(assuming the user has no TSO segment).
3. Every TSO user may or may NOT have rights to manage dataset 
authorities, his own (HLQ=userid) OR OTHER DATASETS.
4. Details depend on your setup. Usually "his own" datasets are in scope 
of the user (userid is the owner of userid.** profile) and that is 
enough to manage access list and UACC.
5. However admin may restrict RACF commands like AD, ALDSD nad PE and 
then user cannot use them to manage rights. There are other methods also.


HTH

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: JES2 Policies

2020-11-11 Thread R.S.


This is matter of the tool used to do mass change.
IMHO there is no rocket science to write some simple REXX script adding 
keyword parameter to existing statement with preserving JCL rules coding.
Of course there is nothing wrong with two step approach - first for 
adding CLASS=existing_default, and second with change this value to other.


BTW: many years ago I supported some "wannabe-programmer" and "wannabe - 
consultant", who was unable to change jobclass.
Yes, the problem was CLASS=5 and his task was to change it to CLASS=A or 
just delete this parameter.
It took him 7 hours and many attempts to surrender ...and demand JES2 
reconfiguration. ;-)
Yes, JCL syntax and ISPF Edit were black magic for him. Few years later 
his company hired me to teach JCL. Usually it takes 4.5 days (IBM 
course), but they demanded to compress it to one day. Oh, students had 
very weak knowledge about ISPF and Edit.


--
Radoslaw Skorupka
Lodz, Poland






W dniu 05.11.2020 o 16:44, Mike Schwab pisze:

Step 1 I would put the default CLASS= in every job.  Easier to change
the default than add a new line.

On Thu, Nov 5, 2020 at 6:09 AM R.S.  wrote:

Now we know more. Maybe still not enough ;-)
However we may assume:
a) there is finite number of the jobs
b) you know all the jobs - that means all PDS/PDSE's with the jobs. No
secret libraries, no forgotten user libraries, etc.
c) the jobs are not generated dynamically by some "black box" tool, so
all the jobs are known.
d) jobs have accnt field with some known/documented format and its
content clearly tell you which class to use (let's simplify it to just
jobclasses A, B, C - good, better, the best)

In such scenario I would think about mass change.
Simply, for any job with ACCNT containing GOOD place CLASS=A. For any
job with ACCNT containing BTTR place CLASS=B, and for each job with BEST
place CLASS=C.

Note: it doesn't matter whether you have 100, 1000 or 1 jobs.
OK, for 100 jobs it is still feasible to change it manually. ;-)

Note2: Since the jobs are already in production, with NO classes, there
is no big problem to change it gradually. Even "forgotten" libraries can
be changed later, when detected.

--
Radoslaw Skorupka
Lodz, Poland






W dniu 05.11.2020 o 06:21, Gadi Ben-Avi pisze:

Hi Everone.
Thanks for responding.

We 'purchased'  a system from another site.
The jobs that came with the system do not have a CLASS parameter specified.
They do have specific values in the accounting fields that are supposed to 
assign the job to specific classes.
I assume they had an exit that did all of this.

Up until now, all of the jobs ran in the same class, with the same service 
class.
I've been asked to assign a lower service class to jobs that have a specific 
(not specified as yet) value in the accounting data.

The simplest way would have been to tell the job owners to code a CLASS 
parameter on the JOB card, but they say that that is too much work.

I looked at doing this using WLM definitions.
It works if the value in the accounting data is in the first 8 bytes.
Otherwise, it get complicated to write, debug, and read.

I read about JES2 Policies, so I looked it up in the documentation.

Gadi


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Jesse 1 Robinson
Sent: Wednesday, November 4, 2020 10:05 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JES2 Policies

In a previous life at the late great Security Pacific, we an *elaborate* scheme 
based on account numbers. Even the job name was generated from account number. 
To control all this, we had a VSAM file containing all valid account numbers 
along with indications of who could submit jobs with each number. An array of 
JES2 and SMF exits were employed to make all this work. At the end of the year, 
account numbers were used for chargeback to respective departments for resource 
usage.

There is no way in h*ll I would recommend this complex scheme for a modern 
shop. But yes, with enough time and $$, it can be done.

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

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Lizette Koehler
Sent: Wednesday, November 4, 2020 10:53 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: JES2 Policies

*** EXTERNAL EMAIL - Use caution when opening links or attachments ***

Initial Request:
The current goal is to change a job's class or service class depending on 
certain values in the accounting information.

It also seems to me that a JCL tool, Like JCLPLUS could put rules into JCL 
Scanning and force users to adhere to a standard.  But that would mean you have 
a Source management system that is used to deploy Jobs to various systems.

It could have rules that say, if Account Code is this, then the job should have 
Service Class STCLOW  and CLASS X


L

Re: JES2 Policies

2020-11-11 Thread R.S.

W dniu 05.11.2020 o 20:01, retired mainframer pisze:

-Original Message-
From: IBM Mainframe Discussion List  On
Behalf Of R.S.
Sent: Thursday, November 05, 2020 4:20 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JES2 Policies

Joe,

And I'm pretty sure no business department is interested in ACCNT field
and its content. Believe me or not: IT is a tool to achieve business
goal, but the details, guts, fields, commas are NOT in the scope of
business focus. They want working application, it is up to IT how to do
it. Changing ACCNT or classes are not strategic.
BTW: Gadi's further explanation sched more light on that.
That's why I proposed solution for real need.  Not just abstract
excercise to solve.

--
Radoslaw Skorupka
Lodz, Poland

Why would you think that?  When I was working, our office had several different contracts active 
simultaneously.  Many were "cost plus" rather than "fixed fee."  It was not 
unusual to spend a portion of each day on different ones.  We were required to daily document our 
time on each to the nearest tenth of an hour.  Similarly, when we logged on to TSO or submitted a 
batch job, we were required to specify the account field that corresponded to that contract.  We 
had an exit (IEFACTRT?) that captured this along with job statistics, such as CPU time, I/O counts, 
etc and cut appropriate SMF records.  These formed the basis for billing the customers.  It was 
also used by management to determine how accurate initial estimates were and then refine our 
process for estimating future bids.

Why do I think that? This is my experience. I saw and *solved* many 
scenarios where weird (OK, unusual) requirements were NOT business need, 
but were derivative of those. Yes, I sustain - business dept has no 
interest in ACCNT field, TRK vs CYL vs AVG and many other technical 
things. BTW: I also saw other scenarios but I have *never* saw 
reasonable explanation for them. Of course this is only my limited 25+ 
yo experience. I would be happy to learn such cases.

BTW: Your case seem ridiculous (tenths of hour? Every job accounted?), 
but - this is more important - it has nothing to do with the problem.
Please, read Gadi's further explanations. In this case the only purpose 
(*) of ACCNT field is to manage job class and service class assignment.

(*)
(Fine print: this is the only purpose we know. However why to suspect 
there are other hidden purposes? How to satisfy them? And what's wrong 
with CLASS= keyword in jobcard?)

--
Radoslaw Skorupka
Lodz, Poland

==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: JES2 Policies

2020-11-05 Thread R.S.


Joe,
This is not my call (honestly I don't know this idiom). This is not my 
dog, this is not my business.

I can leave it with no answer, but my willing is to help.
And part of the help is not to just code the exit, but discuss about 
solution.


And I'm pretty sure no business department is interested in ACCNT field 
and its content. Believe me or not: IT is a tool to achieve business 
goal, but the details, guts, fields, commas are NOT in the scope of 
business focus. They want working application, it is up to IT how to do 
it. Changing ACCNT or classes are not strategic.

BTW: Gadi's further explanation sched more light on that.
That's why I proposed solution for real need.  Not just abstract 
excercise to solve.


--
Radoslaw Skorupka
Lodz, Poland






W dniu 05.11.2020 o 13:05, Joe Monk pisze:

"However I think it not valid
requirement, there is no business need behind it."

Thats not your call to make. They are entitled to run their business how
they see fit.

Joe

On Thu, Nov 5, 2020 at 5:53 AM R.S.  wrote:


W dniu 04.11.2020 o 19:50, Lizette Koehler pisze:

Can RACF see the account code and make a decision?

Obviously not. RACF is also unable to see submitters trousers, check how
many days left to nearest holiday, etc.


That is what (as I understand it) the initial requirement is.

Yes, that requirement was presented to us. However I think it not valid
requirement, there is no business need behind it.
It is more complex: some reasonable business need led to use accnt. And
this is worth to discuss IMHO. Or just go back to business need and
discuss how to satisfy it. To avoid Rube Goldberg machinery.


--
Radoslaw Skorupka
Lodz, Poland




==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: JES2 Policies

2020-11-05 Thread R.S.


Now we know more. Maybe still not enough ;-)
However we may assume:
a) there is finite number of the jobs
b) you know all the jobs - that means all PDS/PDSE's with the jobs. No 
secret libraries, no forgotten user libraries, etc.
c) the jobs are not generated dynamically by some "black box" tool, so 
all the jobs are known.
d) jobs have accnt field with some known/documented format and its 
content clearly tell you which class to use (let's simplify it to just 
jobclasses A, B, C - good, better, the best)


In such scenario I would think about mass change.
Simply, for any job with ACCNT containing GOOD place CLASS=A. For any 
job with ACCNT containing BTTR place CLASS=B, and for each job with BEST 
place CLASS=C.


Note: it doesn't matter whether you have 100, 1000 or 1 jobs.
OK, for 100 jobs it is still feasible to change it manually. ;-)

Note2: Since the jobs are already in production, with NO classes, there 
is no big problem to change it gradually. Even "forgotten" libraries can 
be changed later, when detected.


--
Radoslaw Skorupka
Lodz, Poland






W dniu 05.11.2020 o 06:21, Gadi Ben-Avi pisze:

Hi Everone.
Thanks for responding.

We 'purchased'  a system from another site.
The jobs that came with the system do not have a CLASS parameter specified.
They do have specific values in the accounting fields that are supposed to 
assign the job to specific classes.
I assume they had an exit that did all of this.

Up until now, all of the jobs ran in the same class, with the same service 
class.
I've been asked to assign a lower service class to jobs that have a specific 
(not specified as yet) value in the accounting data.

The simplest way would have been to tell the job owners to code a CLASS 
parameter on the JOB card, but they say that that is too much work.

I looked at doing this using WLM definitions.
It works if the value in the accounting data is in the first 8 bytes.
Otherwise, it get complicated to write, debug, and read.

I read about JES2 Policies, so I looked it up in the documentation.

Gadi


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Jesse 1 Robinson
Sent: Wednesday, November 4, 2020 10:05 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JES2 Policies

In a previous life at the late great Security Pacific, we an *elaborate* scheme 
based on account numbers. Even the job name was generated from account number. 
To control all this, we had a VSAM file containing all valid account numbers 
along with indications of who could submit jobs with each number. An array of 
JES2 and SMF exits were employed to make all this work. At the end of the year, 
account numbers were used for chargeback to respective departments for resource 
usage.

There is no way in h*ll I would recommend this complex scheme for a modern 
shop. But yes, with enough time and $$, it can be done.

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

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Lizette Koehler
Sent: Wednesday, November 4, 2020 10:53 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: JES2 Policies

*** EXTERNAL EMAIL - Use caution when opening links or attachments ***

Initial Request:
The current goal is to change a job's class or service class depending on 
certain values in the accounting information.

It also seems to me that a JCL tool, Like JCLPLUS could put rules into JCL 
Scanning and force users to adhere to a standard.  But that would mean you have 
a Source management system that is used to deploy Jobs to various systems.

It could have rules that say, if Account Code is this, then the job should have 
Service Class STCLOW  and CLASS X


Lizette


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Allan Staller
Sent: Wednesday, November 4, 2020 11:35 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JES2 Policies

Wouldn't RACF jobclass controls be more appropriate?

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of Joe 
Monk
Sent: Wednesday, November 4, 2020 10:31 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JES2 Policies

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don’t click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]

Radoslaw,

I think what the OP is really saying is that certain accounts should be 
restricted from certain jobclasses i.e. DEV cant use PROD jobclasses. So, if 
they code a CLASS=X, but the  account info says  that they dont have access to 
CLASS=X, then dump the job.

OP: This has been around a long time, and is very mature...

Joe

On Wed, Nov 4, 2020 at 8:20 AM R.S.  wrote:


W dniu 04.11.2020 o 13:10, Gadi Ben-Avi pisze:

Hi,
I've started looking into JES2 Policies.

The current goal

Re: JES2 Policies

2020-11-05 Thread R.S.


W dniu 04.11.2020 o 19:50, Lizette Koehler pisze:

Can RACF see the account code and make a decision?
Obviously not. RACF is also unable to see submitters trousers, check how 
many days left to nearest holiday, etc.



That is what (as I understand it) the initial requirement is.
Yes, that requirement was presented to us. However I think it not valid 
requirement, there is no business need behind it.
It is more complex: some reasonable business need led to use accnt. And 
this is worth to discuss IMHO. Or just go back to business need and 
discuss how to satisfy it. To avoid Rube Goldberg machinery.



--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: JES2 Policies

2020-11-05 Thread R.S.


W dniu 04.11.2020 o 19:29, Lizette Koehler pisze:

[...]
I worked in a shop with over 500 exits in JES2/zOS/Vtam etc...   Each upgrade 
took longer to do - basically do to validation of the code.  One upgrade we 
decided to reduce that down and let the system perform its own functions.  Went 
down to 30 exits and the systems worked just fine and upgrade times were faster.


More than 500 exits?
Well, I would have a problem to point where the exits are implemented. 
Not to explain the reasons.


--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: VUE - how to find it?

2020-11-04 Thread R.S.


W dniu 03.11.2020 o 23:19, Attila Fogarasi pisze:

The product announcement letter gives the VUE value.  I have never seen a
consolidated web page for all products/VUEs, you have to look at the
specific announcement letter applicable to your product.  For example for
CICS TS 5.6 it is VUE007.  Luckily its easy to find IBM
announcement letters

On Wed, Nov 4, 2020 at 3:05 AM R.S.  wrote:


This is about IBM software licensing.
For OTC there are VUE - Value Unit Exhibits.
There some non-linear relationship between MSU and VUE number, but there
are several VUE's and the same machine have 300 VUE007, but 350 VUE008,
etc. (Number are examples only).

Now it time for the question: How to find out which VUEnnn is applicable
to given product? Is there any table or other webpage with such
information?

--
Radoslaw Skorupka
Lodz, Poland



It seems you are right, unfortunately there is no such place with VUE to 
product assignment.
However review of LPS or other documents describing VUE assigned to the 
product is really troublesome.

BTW: THANK YOU ROGER FOR YOUR HELP!

Some remarks for record purposes:

1. Some Licensed Product Specifications are available as PDF (good), 
some are available online (average) and some are available as hardcopy 
only (bad!). The last one I read on IBM pages and I really could not 
find the document having its publication ID.
2. VUE calculator is good for calculations, but will not help to know 
which VUE is assigned to given product. This is obsolete tool, it does 
not containt VUE040, which is probably newer than the tool. More, this 
tool has no explanation of term and acronyms used in the VUEs.
3. There is some document (few pages) describing all VUEs I know. It can 
be used instead of calculator, because the formulas are quite simple.
4. Reviewing LPSes and Announcement Letters is not something nice, 
especially you have to pay attention to version of the product! For 
example MFA product changed VUE metrics! It can be really misleading - 1 
VUE for previous version meant 1 user, but for current version it is 
"block of users" which means 500 users. Big difference.
5. VUE itself is loosely related to money. For example popular VUE007 is 
assigned to CICS TS as well as small products like TACM. And of course 
CICS is more expensive. However you can negotiate "price per unit" as 
with gold or potatoes - and then there is a measure for upgrades, etc.
6. Why VUE, but not MSU or users, or terabytes? Simply to have 
degressive prices per real unit. For example firs user is 1 VUE. Second 
user is another 1 VUE, 10 users is 10 VUE, but 1000 users is 800 VUE. 
Same for MSU.


--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: JES2 Policies

2020-11-04 Thread R.S.

First, I still disagree to keep prod and dev on same system. However 
this is different topic.
Second, in your scenario user can put wrong class, but system 
automagically recognize it using ACCNT field.
So - we assume possibility of user mistake in the class coding, but we 
rely on ACCNT field. Why? Is the field protected from mistakes? How?
I don't see any sense here, I'm sorry. When we allow user to use two 
classes but one is for "better" jobs, and the second for "worse" jobs - 
in fact we stil allow user to decide. Or make a mistake.


For simple control of job classes and service classes (that was in the 
question) it is enough to use standard RACF profiles. Why to to 
complicate it?


In fact majority of discussion is based on some assumptions, not real 
and clearly presented needs. That's why I wrote provocating words in my 
previous message (however no offence intended). Just to encourage OP to 
better explanation.


--
Radoslaw Skorupka
Lodz, Poland






W dniu 04.11.2020 o 17:30, Joe Monk pisze:

Radoslaw,

I think what the OP is really saying is that certain accounts should be
restricted from certain jobclasses i.e. DEV cant use PROD jobclasses. So,
if they code a CLASS=X, but the  account info says  that they dont have
access to CLASS=X, then dump the job.

OP: This has been around a long time, and is very mature...

Joe

On Wed, Nov 4, 2020 at 8:20 AM R.S.  wrote:


W dniu 04.11.2020 o 13:10, Gadi Ben-Avi pisze:

Hi,
I've started looking into JES2 Policies.

The current goal is to change a job's class or service class depending

on certain values in the accounting information.

>From reading the manual, it seems that this is possible.

Has anyone done something like this?
Is there a way to debug these policies?

Is this feature mature enough to use?

I dare to disagree ...with your goal. More precisely I disagree with
your presentation of the goal.
Does it really have to depend on account information? Why?

That means user has to code something in the jobcard, in the first
positional. So he may code CLASS= keyword as well, can't he?
Maybe your accnt infor is already somehowe controlled (my guess, lack of
information). However jobclass can be RACF-controlled.
And this is quite mature way to control job classes and (indirectly)
service classes.

--
Radoslaw Skorupka
Lodz, Poland




==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: JES2 Policies

2020-11-04 Thread R.S.


W dniu 04.11.2020 o 13:10, Gadi Ben-Avi pisze:

Hi,
I've started looking into JES2 Policies.

The current goal is to change a job's class or service class depending on 
certain values in the accounting information.
>From reading the manual, it seems that this is possible.

Has anyone done something like this?
Is there a way to debug these policies?

Is this feature mature enough to use?


I dare to disagree ...with your goal. More precisely I disagree with 
your presentation of the goal.

Does it really have to depend on account information? Why?

That means user has to code something in the jobcard, in the first 
positional. So he may code CLASS= keyword as well, can't he?
Maybe your accnt infor is already somehowe controlled (my guess, lack of 
information). However jobclass can be RACF-controlled.
And this is quite mature way to control job classes and (indirectly) 
service classes.


--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: VUE - how to find it?

2020-11-03 Thread R.S.


W dniu 03.11.2020 o 20:36, Roger Lowe pisze:

On Tue, 3 Nov 2020 19:44:52 +0100, R.S.  wrote:


Yes, I know this tool, I have it on my PC desktop, this is good for
MSU->VUE calculations, but it say nothing about which VUE is assigned to
given product.

Note: I'm focusing about MSU-VUE, but there are also other metrics based
on Terabytes (of storage), engines (say processors), users, etc.

--

Would this be of any help? - https://www.ibm.com/downloads/cas/NV5RDQXB


Well, yes and no.
Yes - it is helpful description.
No - it gives absolutely no clue about product to VUE assignment.
However thank you for your willing to help, I appreciate your effort. 
This is important, because this you tried to help and in many cases it 
really helps. Thank you again. And thanks to Parwez, Chris and other 
gentlemen.


It seems I really need to review LPSes which is hard because these 
documents are really hardly available on the Web.

Now I'm looking for:
z/Multi-Factor Auth 5655-MA1 2.1.0
zDMF  5655-ZZ3 3.4.1

I would really like to install it instead...

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: VUE - how to find it?

2020-11-03 Thread R.S.

Yes, I know this tool, I have it on my PC desktop, this is good for 
MSU->VUE calculations, but it say nothing about which VUE is assigned to 
given product.


Note: I'm focusing about MSU-VUE, but there are also other metrics based 
on Terabytes (of storage), engines (say processors), users, etc.


--
Radoslaw Skorupka
Lodz, Poland






W dniu 03.11.2020 o 18:57, Parwez Hamid pisze:

This website talks about some sort of tool for converting to VUE 'values'

https://www.ibm.com/it-infrastructure/z/software/pricing-tools
[https://1.cms.s81c.com/sites/default/files/2019-04-26/z_pricing_bg_leadspace_2.jpg]<https://www.ibm.com/it-infrastructure/z/software/pricing-tools>
Software Pricing Tools for IBM Z Mainframes | 
IBM<https://www.ibm.com/it-infrastructure/z/software/pricing-tools>
Get the toolkit to discover and get started with selected software pricing 
options for IBM Z mainframes.
www.ibm.com


Regards

Parwez Hamid


From: IBM Mainframe Discussion List  on behalf of R.S. 

Sent: 03 November 2020 16:05
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: VUE - how to find it?

This is about IBM software licensing.
For OTC there are VUE - Value Unit Exhibits.
There some non-linear relationship between MSU and VUE number, but there
are several VUE's and the same machine have 300 VUE007, but 350 VUE008,
etc. (Number are examples only).

Now it time for the question: How to find out which VUEnnn is applicable
to given product? Is there any table or other webpage with such
information?

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: VUE - how to find it?

2020-11-03 Thread R.S.


Yes, both may be licensed as MLC or OTC.
For OTC licensing DB2 has VUE001, Omegamon has VUE007, but CICS TS has ???
And this is what I'm looking for.

Sometimes this information can be found in so called LPS (Licensed 
Program Specifications), however it is hard to get softcopy of that 
document.
For exaple I cannot get LPS for z/Multi-Factor Auth 2.1.0 (5655-MA1) or 
zDMF  3.4.1 (5655-ZZ3). However I don't need the LPS, I need the VUE 
number.




Regards
--
Radoslaw Skorupka
Lodz, Poland







W dniu 03.11.2020 o 17:27, Chris Hoelscher pisze:

I cannot answer your question directly, but at our site db2 CICS and MQ all had 
VUE options

Chris Hoelscher
Lead Sys DBA
IBM Global Technical Services on assignmemt to Humana Inc.
T 502.476.2538  or 502.407.7266


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of R.S.
Sent: Tuesday, November 3, 2020 11:05 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [IBM-MAIN] VUE - how to find it?

[External Email: Use caution with links and attachments]


This is about IBM software licensing.
For OTC there are VUE - Value Unit Exhibits.
There some non-linear relationship between MSU and VUE number, but there are 
several VUE's and the same machine have 300 VUE007, but 350 VUE008, etc. 
(Number are examples only).

Now it time for the question: How to find out which VUEnnn is applicable to 
given product? Is there any table or other webpage with such information?

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

VUE - how to find it?

2020-11-03 Thread R.S.


This is about IBM software licensing.
For OTC there are VUE - Value Unit Exhibits.
There some non-linear relationship between MSU and VUE number, but there 
are several VUE's and the same machine have 300 VUE007, but 350 VUE008, 
etc. (Number are examples only).


Now it time for the question: How to find out which VUEnnn is applicable 
to given product? Is there any table or other webpage with such 
information?


--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: VSAM-RLS and DFSMStvs basic questions

2020-11-01 Thread R.S.


W dniu 31.10.2020 o 00:40, Joe Monk pisze:

Radoslaw,

He is asking about shareoption (4 x)  not (x 4) aka cross-region sharing,
not cross-system sharing.

In VSE, Shareoption(4) allows vsam file sharing among partitions (similar
to a z/os address space). VSE manages  that automatically, for the user.


Well, I just learnt something new about VSAM. Thank you.
Actually it is strictly related to z/VSE - this system is unknown for me 
(my research told me there were only two installations in Poland).
For example I don't know what is partition in VSE and how it is differ 
from regular address spaces or just several jobs (in VSE) working with 
same shared VSAM file.


BTW: Few questions
Where can I read about VSAM SHR (4 x)?
Was SHR (4 x) available on MVS or its predecessor?
Is there any "introduction" of VSE disks usage, datasets, and so called 
file system? How is it similar to z/OS?




However, regarding the subject I sustain that migration to Db2 is worth 
to analyze.
Of course everything depends on many factors like appliation complexity, 
staff availability, MIPS in use, budget, plans for the future, etc.


--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: VSAM-RLS and DFSMStvs basic questions

2020-10-30 Thread R.S.


W dniu 30.10.2020 o 23:51, Tony Thigpen pisze:

All,

I have a z/VSE client that believes it is time to move to z/OS. But, 
they have one big concern. They have a lot of ShareOption=4 VSAM files.


For those that don't know it, ShareOption=4 files on z/VSE "work out 
of the box" without any need for the application program to perform 
any enqueue or dequeue. z/VSE automatically performs those functions, 
unlike z/OS where the application has to handle the enqueue process.


In their case, they use shareoption=4 so that they can update VSAM 
files from batch Cobol programs while at the same time CICS Cobol 
programs are also updating the files. They don't want to have to 
change their programs.


From my initial research, it appears that this same function can be 
reproduced on z/OS using DFHSMStvs. (And, it looks like VSAM-RLS is 
also required to support DFHSMStvs.)


Are we going down the right path?


IMHO no.

Some remarks:
1. Any migration will require some work to do. Sometimes little less 
effort give you much worse results.
2. SHR (x 4) means cross-system sharing. Why it is cross-system? Why 
don't you consolidate it into one system? What are the reasons?
3. VSAM RLS is almost free - that means it is not licensed, but it 
require Coupling Facility - even in single system configuration. Such 
kind of Parallel Sysplex. Even when you want to have single CPC, you 
still need CPU engine for CF, that is ICF processor. It is approx. 250k$ 
(for big machine). And some memory. However tvs is not necessary. Note: 
tvs is paid, because there are ISV options. And there are some IBM 
add-ons like CICSVR, etc.
4. Let's go back to point 1 - maybe it is good time to move from VSAM to 
Db2? Note, there is special software product which allow VSAM 
application to work with Db2 with minimal changes. And of course you 
would have a lot of Db2 advantages over VSAM, and any new development 
could directly interface with Db2, not Db2 under cover of VSAM. Of 
course neither the product, nor Db2 is free, but...



--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: Generic name for PDS/PDSE

2020-10-28 Thread R.S.


W dniu 28.10.2020 o 18:25, Jesse 1 Robinson pisze:

Radoslaw, I would be happy to have you as my teacher.


You are very kind, thank you.
In fact I really love teaching.
IMHO this is crucial - when you do what you like, usually you do it well.
I was teaching maths, physics, chemistry, and mechanics (!) before I 
graduated. I was lecturer in some university also.
However IT courses are better as part time duty and much closer to scope 
of my interest. Because you have to know the subject. ;-)


Regards
--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: How best to copy all UNIX files one z/OS to another

2020-10-28 Thread R.S.


W dniu 28.10.2020 o 17:52, Charles Mills pisze:

I have two z/OS systems joined by a real fast TCP connection. (They're
actually two guests on the same VM, but seeing as how I have relatively
little knowledge or authority on the VM side of things it may be simpler to
just think of them as two adjacent machines.) This is the IBM Dallas
"Innovation Center," FWIW.

  


What would be the best way of replicating all of the "user" UNIX files from
one to the other? I can of course identify the "user" files by their highest
directory name. I want to propagate all of the permissions and so forth. Is
there a good way to do that?

  


FWIW I have complete authority on the z/OS machines; I can run SPECIAL
and/or OPERATIONS if necessary.

  


Related question: the UNIX file system on the "old" machine is a hodgepodge
of VSAM LDS. Every time we needed a bunch more space we simply defined a big
enough VSAM LDS and mounted it as whatever we needed. There's no advantage
to keeping the existing structure, is there? I should just define a single
space big enough to hold everything? I have no idea what the future might
hold but I don't think the UNIX file inventory is going to shrink
significantly.

  


Thanks, all.

  


Charles

  



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



There are many ways.
I would suggest two:
1. Just "dump" your files, whol directory subtree to a file using pax 
utility. Very simple, preserves all the attributes.

Of course this is dump-restore, or dump-send_file-restore.

2. Assuming all you files reside in single filesystem, just unmount it 
and dump as any other VSAM dataset. Then copy it to target system, 
restore and mount.
Disadvantate: this is all-or-nothing method and even free space have to 
be moved. For almost-empty filesystems it is not effective.


--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: Generic name for PDS/PDSE

2020-10-28 Thread R.S.


W dniu 28.10.2020 o 18:00, Paul Gilmartin pisze:

On Wed, 28 Oct 2020 16:09:27 +, Frank Swarbrick wrote:


Load module or program object should be easy: executable, or binary executable.


Does this include "executable" residing in a UNIX directory?  Must this be
further clarified, perhaps to prohibit:
 //STEP  EXEC  PGM='/bin/true'


This is part of JCL course.
And my explanation seems like this:
You provide MEMBER NAME. The program is a member of PDS or PDSE library. 
What library? There is some system list, similar to PATH in 
Unix/Windows/DOS/OS2. However you may provide your own libary but NOT 
HERE. Here is a place of member name only.

Name of library is in STEPBLIB DD (and JOBLIB DD...)
Q: "Radek, what about unix system services programs"?
A: "this is about native MVS programs. We learn this part now. Unix 
program can be called, but this is in next part".


BTW: How many times I saw //STEP1  EXEC PGM=USER.MY.LIB(PRG1)
And you know? It doesn't work. ;-)

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: Generic name for PDS/PDSE

2020-10-28 Thread R.S.


Executable - that could mean REXX or CLIST.
In fact people usually say:
load module - nevermind what is proper name of member/program in PDSE
binary - could be ambiguous
binary program - better a little
EXE files/members - just analogy to PC-DOS or Windows world
compiled program - one could discuss it is compiled and linked.
RECFM=U library - usually correct, but generally speaking incorrect.

IMHO it is IBM fault.
For such cases it is IBM role to give us "the only proper name", just to 
simplify communication and make manuals more clear.
Let's imagine some neologism like BINLOAD - for binary programs, a 
MEMLIB for PDS or PDSE, and BINLIB as MEMLIB for BINLOADs.


I used to teach z/OS basics a lot, so I had to clarify such issues in 
limited timeframe and the explanation has to be clear, not covering all 
possible nuances and cases.
BTW: Covid stopped classes completely so I miss teaching. Not because of 
money, but I miss contact with people, discussions, etc.


--
Radoslaw Skorupka
Lodz, Poland






W dniu 28.10.2020 o 17:09, Frank Swarbrick pisze:

Load module or program object should be easy: executable, or binary executable.


From: IBM Mainframe Discussion List  on behalf of Seymour J 
Metz 
Sent: Wednesday, October 28, 2020 8:48 AM
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: Generic name for PDS/PDSE

I use "PDS(E)", but what's the generic for "load module or program object"?

I spell auto-correct as "auto-defect"; we hates it, precious. Of course, some of the 
"corrections" are hilarious.

I would interpret "MVS library" as DSNTYPE=LIBRARY, but I wouldn't bet on that 
being correct.


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


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Charles Mills [charl...@mcn.org]
Sent: Tuesday, October 27, 2020 5:44 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Generic name for PDS/PDSE

Grrr. As a frequent writer of documentation I struggle with that one.

I would say either "PDS(E)" (which my PC keeps trying to auto-correct to PDS) 
or a preamble something like

"In this document, the term PDS means either a Partitioned Dataset (PDS) or a 
Partitioned Dataset Extended (PDSE) unless the context clearly demands otherwise."

I personally at least would have to think "what the heck does he mean?" every time I 
encountered "MVS library."

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Frank Swarbrick
Sent: Tuesday, October 27, 2020 2:17 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Generic name for PDS/PDSE

Is there a standard "generic" name for PDS/PDSE?  Is it "PDS(E)"?  Or maybe something like 
"MVS library" or "MVS dataset library"?





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: Generic name for PDS/PDSE

2020-10-28 Thread R.S.

W dniu 27.10.2020 o 22:17, Frank Swarbrick pisze:

Is there a standard "generic" name for PDS/PDSE? Is it "PDS(E)"? Or maybe something like
"MVS library" or "MVS dataset library"?

Just wondering.

Unfortunately no.
There are some names, but no "the only standard".
Some names in use:
PDS - but also PDSE, which is not clear
PDS/PDSE - quite obvious
PO, DSORG=PO - usually clear, but there is also HFS, which is completely
different animal.
library - misleading. Sometimes it means "dataset with members",
sometimes it is DSNTYPE=LIBRARY which means PDSE, sometimes it means
PDS/PDSE with load modules/programs.

The same problem with unix filesystems - usually called HFS, but there
is HFS (DSORG=PO,DSNTYPE=HFS) and ZFS (VSAM LDS).

In every case the context is important. And in case of doubt, just
explanation is needed.

--
Radoslaw Skorupka
Lodz, Poland

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

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

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

If you are not the addressee of this message:

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

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

Re: Syncsort to DFSORT - my time has come.

2020-10-27 Thread R.S.


W dniu 27.10.2020 o 18:16, Gibney, Dave pisze:

A fairly quick question. Are there sample ICEPRMxx members provided by IBM 
for tailoring DFSORT? I don't find any in SICESAMP.
Yesterday, in my sandbox, I IPL'd with SICELPA, SORTLPA, SICELINK, SORTLIB 
ahead of the SYNCSORT libraries and not ICEPRMxx. SHOWZOS shows DFSORT as 
resident sort program. All seems well. I don't keep this concatenation, it was 
just easier for fall back considerations.


If you want some sample I can send it.
However there is no black magic there.
IMHO it is fundamental to define your needs, because the member is for 
defaults which can be easily overtyped by parameters in the job.


Here you are:

***
** History of changes:
** 05-10-2019 R.SKORUPKA first customization
** dd-mm- user description...
**

*
* JCL (ICEAM1)
JCL
DYNALOC=(3390,10)
*
* INV (ICEAM2)
INV
DYNALOC=(3390,10)



--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: SMF to capture user login history

2020-10-26 Thread R.S.


W dniu 26.10.2020 o 18:14, Charles Mills pisze:

No. The OP did not specify TSO (or any other subsystem). The OP wrote "I would like 
to fetch a user's logon history like when he was logged with all time intervals."



I have no time to check it, so I may be wrong, but I believe every logon 
cut SMF80 with RACINITI.
Note: in order to check it one should logon using all available ways - 
job, TSO, ftp, RMF, CICS, DRDA, telnet, ssh, console, whatever. And then 
make IRRADU00 report and find all the cases.


Remarks:
1. Unsuccesful logon is visible quite better - ICH408I in syslog. 
However it is not the same as succesful logon.
2. Logoff is much more complex - especially when user forgot to logoff 
and left the session.
3. I'm not sure but maybe UAUDIT makes more traces of the logon. 
Obviously it will not change the past.


--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: SMF to capture user login history

2020-10-26 Thread R.S.


Yes, obviously!
But ...no.

To explain: there is an option in RACF, called GRPLIST. Vast majority of 
installations use GRPLIST, but few use NOGRPLIST.


1. YES
For NOGRPLIST you may belong to meny group, but only one connection at 
the time is "active"  - that means you logon as Frank, FRANK1 (that's 
the password) and NETADM - that's the group.

And you have all the authorities given to user FRANK and to group NETADM.
However you are member of SMSADM as well - but this group gives you no 
authorities, because only one group is taken.

Is it stupid? Some people say it is good. Let's leave it.


2. NO
In typical GRPLIST world you logon as FRANK/FRANK1 and (usually) it 
doesn't matter what group you provide, if any.
And you have all the authorities given to FRANK, NETADM, SMSADM and all 
other groups you are connected to.

So, it in this case privileges are not different.

Exception: there are very few, very rare cases when "current connect 
group" is important even in GRPLIST. See ARCCATGP (DFSMShsm manual). 
However AFAIR it is enough to provide this groupname during logon.


Remark: no group provided = default group. Every RACF user has default 
group assigned. And of course the user is connected to this group.


HTH

--
Radoslaw Skorupka
Lodz, Poland






W dniu 26.10.2020 o 17:30, Frank Swarbrick pisze:

Curious question.  Is it possible to have a single user ID with different 
privileges depending on what group you specify when logging in (to TSO, for 
example)?


From: IBM Mainframe Discussion List  on behalf of Seymour J 
Metz 
Sent: Sunday, October 25, 2020 8:05 AM
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: SMF to capture user login history


two sets of IDs

Multiple ids can be very usefull. If you have a lot of privileges and write 
code that is supposed to work without those privileges, it's useful to have a 
bare bones userid. If you have work that requires privileges that you consider 
too dangerous for normal work, it's nice to have a more privileged userid and 
proxy permission. BTDT, GTTS.


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


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Steve Horein [steve.hor...@gmail.com]
Sent: Sunday, October 25, 2020 9:00 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SMF to capture user login history

On Sun, Oct 25, 2020 at 1:11 AM kekronbekron <
02dee3fcae33-dmarc-requ...@listserv.ua.edu> wrote:


I hope no one encourages this kind of snooping on the list.
Stinks of an attempt to police working hours.

- KB





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: SMF to capture user login history

2020-10-26 Thread R.S.


Yes,
To be correct and accurate: z/OS with RACF. And correct SMF 
customization - that means SMF30 and SMF80 are collected. And SMF data 
are archived.
That mean one may read SMF archives using IRRADU00. The output is (huge) 
text file, quite well described in RACF Macros and Interfaces manual. 
The one can use ICETOOL (separetely another licenced program!) or any 
other tool to extract relevant records and format the report.


Regarding legal point of view - this is another issue, it is not related 
to mainframe. However I can imagine valid reasons to prepare such 
report, even just for problem solving.


--
Radoslaw Skorupka
Lodz, Poland






W dniu 25.10.2020 o 16:16, Charles Mills pisze:

Also assuming you run RACF, not either of the CA security products. IRRADU00 is technical 
not "free," it is a part of RACF.

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Charles Mills
Sent: Sunday, October 25, 2020 7:29 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SMF to capture user login history

Yes! Does a good job, again assuming you are collecting the relevant SMF 30 data. 
IRRADU00 contrary to what you might expect from the name processes SMF 30 as well as RACF 
SMF 80 (assuming I recall correctly). It solves the "section" problem that 
@Lizette alludes to. Its output IIRC is a file of huge fixed-layout records. I have never 
used it; this is from customer discussions and documentation-reading.

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of R.S.
Sent: Saturday, October 24, 2020 11:47 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SMF to capture user login history

The answer is IRRADU00 report - standard (free) RACF tool.
Then you can write yoour own report.

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



==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: emptying a PDS: was RE: [IBM-MAIN] getting XCFAS down

2020-10-26 Thread R.S.


W dniu 25.10.2020 o 14:44, Peter Relson pisze:


BTW2: I even experienced F37 abend in the past. It was related to huge
(at the time) Jaguar J1A tapes and good compression and ...problems in
RMM. AFAIK I put over 6TB (terabytes) of uncompressed data on 300GB cart.


Interesting. That completion code would not have been in correct IBM code
(Fxx abends have indicated the non-availability of SVC xx, for as long as
the SVC FLIH has existed, as far as I know).


It was many moons ago, maybe it was z/OS 1.4 or earlier (OS/390 2.10?).
Definitely it was RMM problem, described in some APAR. Jaguar J1A was 
relatively new at the time and capacity growth was signigicant when 
compared to MAGSTAR 3590-H. AFAIR the problem was related to "number of 
bytes written" field in RMM, counter overflow.

Regarding F37 - I just used google and found some cases of RMM & F37.
BTW: google say F16 is not abend. ;-)

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

Re: SMF to capture user login history

2020-10-25 Thread R.S.


The answer is IRRADU00 report - standard (free) RACF tool.
Then you can write yoour own report.

--
Radoslaw Skorupka
Lodz, Poland





==

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

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

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

If you are not the addressee of this message:

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

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

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

1 2 3 4 5 6 7 8 9 10 >

1 - 100 of 1921 matches

Mail list logo