Re: Licensed source code

2020-05-19 Thread Seymour J Metz
Thanks; I pointed at the Landley site. The citation needed tag doesn't refer to 
any particular epoch, so that letter should serve. 


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


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Tony Harminc [t...@harminc.net]
Sent: Tuesday, May 19, 2020 9:22 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Licensed source code

On Mon, 18 May 2020 at 22:54, Seymour J Metz  wrote:

> Does anybody have an announcement or other document that I can cite for
> "The source code is covered by a non-disclosure agreement or a license that
> allows, for example, study and modification, but not redistribution." in
> the wikipedia article [[Proprietary software]] to document IBM's licensed
> terms for the optional source code of a program product. It doesn't matter
> which product, but it would be nice if the document were publicly available
> online. Thanks.
>

If you search for the phrase "Restricted Materials of IBM" you'll find some
appropriate hits. IIRC this wording came into use only as part of OCO, and
applied to the remaining source code that came with the OCO modules.

The hit at 
http://secure-web.cisco.com/1vcqE9rYd4hSoSAMCYR1RfhZCad8CqSJw1CJkhJEPb8cQ6YgEzyAxEhCePjuJIm_8MoRBCCxbGOm2p853-OxGxfcd5Qyk5GbaiF8GOiGCNhSxpLh-ciBE2pRW3fixUSuguf5kRIu0wYDIHYsTw04DZlx56eSjuBsZOWXkA2BQ2srWnLOfn_rN-i_CGAKaQUdYGWNBAzUYqCxGmjvG1MIWDIbZWszO-qynIdJUzI6vg5hwb2AIYMVROa5Ws1CdZZQXTApRcloAd5v1bzlBJCEjEkDkzW8ltba2Uew3FfULZxR9A13_exZmfQ6kCpmyfiIFg8BA4QaT-R_1-R_OmjAHzPsoGUBdyvDt5UaqwUPIQjZkSuvOHHiixjl6PtUd5p9KRUQHqaTeMjhqr1MnQuKZeN830AEcgon8h5L0BTH7W2TNbDCDspOE5aUWc-kuDzSH/http%3A%2F%2Fwww.landley.net%2Fhistory%2Fmirror%2Fibm%2Foco.html
 appears to be
IBM's 1983 OCO announcement. Obviously it would be nicer to have an ibm.com
source for such a thing, but of course an IBM source is probably more
likely to be moved or deleted! And to my recollection the Wayback Machine
honours robots.txt instructions, and IBM has those on almost everything.

But it is here for now - not formatted as nicely as the landley.net
version:
https://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/6/897/ENUS283-016/index.html&request_locale=en

Naturally this doesn't cover the regime(s) for source code predating the
OCO announcement.

Tony H.

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

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


Re: 3270 terminals: CUT vs. DFT

2020-05-19 Thread Tony Harminc
On Mon, 11 May 2020 at 14:17, Alexander Huemer 
wrote:


> Now, the friendly person who created oec says that the 3290 is a so
> called DFT (Distributed Function Terminal), in contrast to a CUT
> (Control Unit Terminal). Most 3270 terminals seem to be of the (simpler)
> CUT variant. oec only works with CUT terminals. Extending the
> functionality to enable it to work with DFT terminals isn't trivial.
>
> Does anybody on the list here know of additional documentation besides
> what's mentioned at [3] that could be helpful to implement DFT support?
>
> What would also be very helpful is a protocol trace of any kind of the
> communication between a 3174 and a DFT terminal.
>

Someone to try to track down is Pierre Goyette, formerly of McGill
University. He wrote what eventually became Hummingbird's TN3270 product,
and I remember, probably in the late 1980s, discussing some details of DFT
that he had reverse engineered.
http://reporter-archive.mcgill.ca/Rep/r2909/humming.html

Wikipedia says that Hummingbird is now a subsidiary of OpenText, but I have
no idea if Pierre is still there or if they still sell 3270 solutions of
any kind.I haven't seen him for many years.

Tony H.

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


Re: Licensed source code

2020-05-19 Thread Tony Harminc
On Mon, 18 May 2020 at 22:54, Seymour J Metz  wrote:

> Does anybody have an announcement or other document that I can cite for
> "The source code is covered by a non-disclosure agreement or a license that
> allows, for example, study and modification, but not redistribution." in
> the wikipedia article [[Proprietary software]] to document IBM's licensed
> terms for the optional source code of a program product. It doesn't matter
> which product, but it would be nice if the document were publicly available
> online. Thanks.
>

If you search for the phrase "Restricted Materials of IBM" you'll find some
appropriate hits. IIRC this wording came into use only as part of OCO, and
applied to the remaining source code that came with the OCO modules.

The hit at http://www.landley.net/history/mirror/ibm/oco.html appears to be
IBM's 1983 OCO announcement. Obviously it would be nicer to have an ibm.com
source for such a thing, but of course an IBM source is probably more
likely to be moved or deleted! And to my recollection the Wayback Machine
honours robots.txt instructions, and IBM has those on almost everything.

But it is here for now - not formatted as nicely as the landley.net
version:
https://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/6/897/ENUS283-016/index.html&request_locale=en

Naturally this doesn't cover the regime(s) for source code predating the
OCO announcement.

Tony H.

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


Re: Question on wrapped JESMSGLG messages

2020-05-19 Thread Seymour J Metz
> It's not the opposite.

You wrote "Messages in z/OS do not wrap and are not formatted." That's an 
unqualified statement. It doesn't say that spliiting only takes place at the 
last minute.

> WTO's don't add a line to an outstanding WTO. 

What is CONNECT, chopped liver?

",CONNECT=connect field
 Specifies a field containing the 4-byte message ID of the previous WTO to 
which this WTO is to be
 connected. This message ID is obtained as an output parameter (returned in 
register 1) from the
 previous WTO. If a register is used, it contains the address of the message ID.
 CONNECT is valid only for continuation of multiple-line messages. When you 
specify this parameter in
 the list form, code it as CONNECT= with nothing after the equal sign."


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


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Jon 
Perryman [jperr...@pacbell.net]
Sent: Tuesday, May 19, 2020 5:08 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Question on wrapped JESMSGLG messages

 On Monday, May 18, 2020, 05:49:43 PM PDT, Seymour J Metz  
wrote: >> Messages in z/OS do not wrap and are not formatted.
> In the nextt paragraph you say the opposite.

It's not the opposite. Consol address space builds a line that is destination 
dependent. Compare the same message in syslog versus joblog. If that line will 
not fit in the space available for that destination, then consol will split the 
line. Destinations such as TSO CONSOLE shouldn't split lines since the buffer 
should be large enough for the largest line.
>> Multi-line messages are multiple MLWTO's
> No, it's generally what its name suggests, a single WTO that specifies 
> multiple lines of text, > although there is a CONNECT parameter that allows 
> you to add a line to an outstanding WTO.
WTO's don't add a line to an outstanding WTO. Each message in a WTO is 
presented to the SSI as a separate message.
The OP wanted to know about multi-line message and how they are formatted. The 
op needs to understand that messages are not formatted in any way by WTO or 
CONSOL. In fact, each message is not validated and may contain invalid hex 
values. All formatting is performed prior to issuing the WTO. The op should 
also understand that the line wrap they  see in syslog occurs because the line 
does not fit in the destination.
The number added to the line identifies a group of messages (mlwto) because 
they may be interspersed with other messages. There are cases where messages 
have occurred days after the first line in an MLWTO.
>> z/OS messages and codes.
> There is a z/OS MVS System Messages Volume 1 (ABA - AOM) that describes 
> message formats.
For the OP, this section may answer other questions.

Jon.

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

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


Re: Question on wrapped JESMSGLG messages

2020-05-19 Thread Jon Perryman
 On Monday, May 18, 2020, 05:49:43 PM PDT, Seymour J Metz  
wrote: >> Messages in z/OS do not wrap and are not formatted.
> In the nextt paragraph you say the opposite.

It's not the opposite. Consol address space builds a line that is destination 
dependent. Compare the same message in syslog versus joblog. If that line will 
not fit in the space available for that destination, then consol will split the 
line. Destinations such as TSO CONSOLE shouldn't split lines since the buffer 
should be large enough for the largest line.
>> Multi-line messages are multiple MLWTO's 
> No, it's generally what its name suggests, a single WTO that specifies 
> multiple lines of text, > although there is a CONNECT parameter that allows 
> you to add a line to an outstanding WTO.
WTO's don't add a line to an outstanding WTO. Each message in a WTO is 
presented to the SSI as a separate message. 
The OP wanted to know about multi-line message and how they are formatted. The 
op needs to understand that messages are not formatted in any way by WTO or 
CONSOL. In fact, each message is not validated and may contain invalid hex 
values. All formatting is performed prior to issuing the WTO. The op should 
also understand that the line wrap they  see in syslog occurs because the line 
does not fit in the destination. 
The number added to the line identifies a group of messages (mlwto) because 
they may be interspersed with other messages. There are cases where messages 
have occurred days after the first line in an MLWTO. 
>> z/OS messages and codes.
> There is a z/OS MVS System Messages Volume 1 (ABA - AOM) that describes 
> message formats.
For the OP, this section may answer other questions.

Jon.  

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


Re: Creating new SMS environment in a monoplex

2020-05-19 Thread Vernooij, Kees (ITOP NM) - KLM
I can confirm that.
We have 2 sysplexes (Prod and Test), both with 2 GPDS K-systems. 
GDPS K-systems don's share Dasd with the other systems of the sysplex.
So we have 6 SMS environments, each with their own SCDS, ACDS and COMMDS.
We have 1 SMS configuration that covers all systems and in the ACS routines, we 
route datasets to storage groups, depending on the system it runs on.
We update the 'source' SMS configuration on the test sysplex systems, activate 
it on the 3 SMS environments in the Test Sysplex and test it. 
Then we transfer the SCDS to the 3 SMS environments of the Prod Sysplex and 
activate it there.
We have no problem with this setup. The advantage is that you don't make typo's 
when trying to copy the updates in the test-environment to the prod-environment.

Kees.

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Richards, Robert B.
Sent: 19 May 2020 17:58
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Creating new SMS environment in a monoplex

Thanks, Radoslaw.

My point, and I think you have also confirmed it, is that an SMS environment 
has no specific dependence on a parallel sysplex, CFs, couple datasets, etc.

All that is left for me is to finish building the system and IPL it.

Bob


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of R.S.
Sent: Tuesday, May 19, 2020 11:21 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Creating new SMS environment in a monoplex

W dniu 18.05.2020 o 20:36, Richards, Robert B. pisze:
> It has been a few decades since I have created a new SMS environment.
>
> Current environment is parallel sysplex replete with CFs and lots of lpars.
>
> I am trying to create a simple SMS environment that will be part of a 
> monoplex consisting on one lpar.
>
> I did the following:
>
>
>1.  Defined the new SYSNAME into the base configuration in ISMF and 
> activated same. D SMS verified it was defined and not active
>2.  A REPRO of the SCDS into a new SCDS dataset (Alter/newname to correct 
> usercat)
>3.  Issued a SETSMS SAVEACDS(also using a SSA connector that I 
> subsequently ALTER NEWNAME the new ACDS into a new usercat that is connected 
> to a new mastercat)
>4.  Defined an empty COMMDS that I also performed an alter/newname to get 
> the desired COMMDS dataset name.
>
> My boss says the ACDS is aware of the original sysplex environment and my 
> gyrations of trying to make the above work in a monoplex will not succeed.
>
> Who is right? Will it work or not?

Quick and dirty method:
1. Add new system name to existing SCDS and ACDS. Don't worry, it is nothing 
wrong to have non-present system names there.
2. Copy all *CDS to disk belonging to new system.
3. IPL the system.

Of course this is method for some migration. ACS routines, class definitions 
and library definitions will be moved. Is that what you want?
Otherwise there is another method, to start from scratch. ACS routines can be 
easily imported, class definitions - the only way I know is to re-define them 
manually.
BTW: some dummy SMS environment is delivered with ServerPac. I always start 
from that point. Then IPL with CPAC system name, then add my name to ACDS then 
reIPL with my system name. Then *CDS datasets can be imported (copied). Piece 
of cake.

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

--

Re: Licensed source code

2020-05-19 Thread Seymour J Metz
I'm not sure that will be good enough for wiki. I recall some very specific 
language on the program directories for the optional source tapes, back when 
there were such things, that would be ideal if I could link to a copy.


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


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Jon 
Perryman [jperr...@pacbell.net]
Sent: Tuesday, May 19, 2020 2:17 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Licensed source code

 On Monday, May 18, 2020, 10:18:10 PM PDT, Seymour J Metz  
wrote:

 > Is there optional source code for any IBM software announced or released 
 > after May, 1999? > I didn't see anything there that related to permissible 
 > and impermissible use of source code.

Macro's are source. I'm not a lawyer but I believe they are considered 
protected material. While not specifically mentioned, they will be covered by 
more than one clause. For instance, making copies of distributed licensed 
material or redistributing licensed material.
Jon.

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

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


Re: Licensed source code

2020-05-19 Thread Jon Perryman
 On Monday, May 18, 2020, 10:18:10 PM PDT, Seymour J Metz  
wrote:
 
 > Is there optional source code for any IBM software announced or released 
 > after May, 1999? > I didn't see anything there that related to permissible 
 > and impermissible use of source code.

Macro's are source. I'm not a lawyer but I believe they are considered 
protected material. While not specifically mentioned, they will be covered by 
more than one clause. For instance, making copies of distributed licensed 
material or redistributing licensed material.
Jon.   

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


Re: tcpip or telnet

2020-05-19 Thread Jon Perryman
 Generic response time monitoring for TCP is not possible. You need to set 
expectations based on the monitors you decide to use. 
To understand the problem, think about what is considered a delay. TN3270 
delays are clearly defined (press enter to screen returned). The Unix 
equivalent is telnet which takes a different approach. Every user keystroke is 
sent to the host application and does not expect a response. At some point, the 
application will decide to send a response for reasons only known to the 
application. Telnet does not have 2 points in time to be measured. 
Your best resource for information and help will probably be your TCP network 
people. They understand your environment and may have tools that meet your 
needs. They may be better positioned to do some of the monitoring because they 
are aware of TCP environmental changes. Worst case, they can help set 
expectations.  
Jon.On Tuesday, May 19, 2020, 05:51:45 AM PDT, Shelia Chalk 
 wrote:  
 
 I don't know were to start, but i will try to explain what i am looking for... 
tcpip i am looking batch job or command that will produce a report to see if i 
have got any connections very slow or over loaded.. if there is such a thing. i 
want to find any connection that has a delay and a report gives me that 
information..

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

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


Re: Creating new SMS environment in a monoplex

2020-05-19 Thread Richards, Robert B.
Skip,

I think the point my boss was trying to make is that there is residual 
information stored in the Parallel Sysplexed ACDS that makes a SAVEACDS copy of 
it unusable for use on a monoplex.

I begged to differ and posted here to see what others thought. I added the new 
lpar's system name into the base configuration and activated it prior to 
issuing the SAVEACDS. When I perform an IPL of the new system, I expect it to 
recognize that system name and a D SMS to show it active while all the other 
system names will show hyphens and N/A under Interval Seconds.

Bob

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Jesse 1 Robinson
Sent: Tuesday, May 19, 2020 1:19 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Creating new SMS environment in a monoplex

We have both parallel sysplexes and monoplexes. SMS runs on every image. 

.
.
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 
Richards, Robert B.
Sent: Tuesday, May 19, 2020 8:58 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Creating new SMS environment in a monoplex

CAUTION EXTERNAL EMAIL

Thanks, Radoslaw.

My point, and I think you have also confirmed it, is that an SMS environment 
has no specific dependence on a parallel sysplex, CFs, couple datasets, etc.

All that is left for me is to finish building the system and IPL it.

Bob


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of R.S.
Sent: Tuesday, May 19, 2020 11:21 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Creating new SMS environment in a monoplex

W dniu 18.05.2020 o 20:36, Richards, Robert B. pisze:
> It has been a few decades since I have created a new SMS environment.
>
> Current environment is parallel sysplex replete with CFs and lots of lpars.
>
> I am trying to create a simple SMS environment that will be part of a 
> monoplex consisting on one lpar.
>
> I did the following:
>
>
>1.  Defined the new SYSNAME into the base configuration in ISMF and 
> activated same. D SMS verified it was defined and not active
>2.  A REPRO of the SCDS into a new SCDS dataset (Alter/newname to correct 
> usercat)
>3.  Issued a SETSMS SAVEACDS(also using a SSA connector that I 
> subsequently ALTER NEWNAME the new ACDS into a new usercat that is connected 
> to a new mastercat)
>4.  Defined an empty COMMDS that I also performed an alter/newname to get 
> the desired COMMDS dataset name.
>
> My boss says the ACDS is aware of the original sysplex environment and my 
> gyrations of trying to make the above work in a monoplex will not succeed.
>
> Who is right? Will it work or not?

Quick and dirty method:
1. Add new system name to existing SCDS and ACDS. Don't worry, it is nothing 
wrong to have non-present system names there.
2. Copy all *CDS to disk belonging to new system.
3. IPL the system.

Of course this is method for some migration. ACS routines, class definitions 
and library definitions will be moved. Is that what you want?
Otherwise there is another method, to start from scratch. ACS routines can be 
easily imported, class definitions - the only way I know is to re-define them 
manually.
BTW: some dummy SMS environment is delivered with ServerPac. I always start 
from that point. Then IPL with CPAC system name, then add my name to ACDS then 
reIPL with my system name. Then *CDS datasets can be imported (copied). Piece 
of cake.

--
Radoslaw Skorupka
Lodz, Poland


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

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


Re: Creating new SMS environment in a monoplex

2020-05-19 Thread Jesse 1 Robinson
We have both parallel sysplexes and monoplexes. SMS runs on every image. 

.
.
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 
Richards, Robert B.
Sent: Tuesday, May 19, 2020 8:58 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Creating new SMS environment in a monoplex

CAUTION EXTERNAL EMAIL

Thanks, Radoslaw.

My point, and I think you have also confirmed it, is that an SMS environment 
has no specific dependence on a parallel sysplex, CFs, couple datasets, etc.

All that is left for me is to finish building the system and IPL it.

Bob


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of R.S.
Sent: Tuesday, May 19, 2020 11:21 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Creating new SMS environment in a monoplex

W dniu 18.05.2020 o 20:36, Richards, Robert B. pisze:
> It has been a few decades since I have created a new SMS environment.
>
> Current environment is parallel sysplex replete with CFs and lots of lpars.
>
> I am trying to create a simple SMS environment that will be part of a 
> monoplex consisting on one lpar.
>
> I did the following:
>
>
>1.  Defined the new SYSNAME into the base configuration in ISMF and 
> activated same. D SMS verified it was defined and not active
>2.  A REPRO of the SCDS into a new SCDS dataset (Alter/newname to correct 
> usercat)
>3.  Issued a SETSMS SAVEACDS(also using a SSA connector that I 
> subsequently ALTER NEWNAME the new ACDS into a new usercat that is connected 
> to a new mastercat)
>4.  Defined an empty COMMDS that I also performed an alter/newname to get 
> the desired COMMDS dataset name.
>
> My boss says the ACDS is aware of the original sysplex environment and my 
> gyrations of trying to make the above work in a monoplex will not succeed.
>
> Who is right? Will it work or not?

Quick and dirty method:
1. Add new system name to existing SCDS and ACDS. Don't worry, it is nothing 
wrong to have non-present system names there.
2. Copy all *CDS to disk belonging to new system.
3. IPL the system.

Of course this is method for some migration. ACS routines, class definitions 
and library definitions will be moved. Is that what you want?
Otherwise there is another method, to start from scratch. ACS routines can be 
easily imported, class definitions - the only way I know is to re-define them 
manually.
BTW: some dummy SMS environment is delivered with ServerPac. I always start 
from that point. Then IPL with CPAC system name, then add my name to ACDS then 
reIPL with my system name. Then *CDS datasets can be imported (copied). Piece 
of cake.

--
Radoslaw Skorupka
Lodz, Poland


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


Re: Creating new SMS environment in a monoplex

2020-05-19 Thread Richards, Robert B.
Thanks, Radoslaw.

My point, and I think you have also confirmed it, is that an SMS environment 
has no specific dependence on a parallel sysplex, CFs, couple datasets, etc.

All that is left for me is to finish building the system and IPL it.

Bob


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of R.S.
Sent: Tuesday, May 19, 2020 11:21 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Creating new SMS environment in a monoplex

W dniu 18.05.2020 o 20:36, Richards, Robert B. pisze:
> It has been a few decades since I have created a new SMS environment.
>
> Current environment is parallel sysplex replete with CFs and lots of lpars.
>
> I am trying to create a simple SMS environment that will be part of a 
> monoplex consisting on one lpar.
>
> I did the following:
>
>
>1.  Defined the new SYSNAME into the base configuration in ISMF and 
> activated same. D SMS verified it was defined and not active
>2.  A REPRO of the SCDS into a new SCDS dataset (Alter/newname to correct 
> usercat)
>3.  Issued a SETSMS SAVEACDS(also using a SSA connector that I 
> subsequently ALTER NEWNAME the new ACDS into a new usercat that is connected 
> to a new mastercat)
>4.  Defined an empty COMMDS that I also performed an alter/newname to get 
> the desired COMMDS dataset name.
>
> My boss says the ACDS is aware of the original sysplex environment and my 
> gyrations of trying to make the above work in a monoplex will not succeed.
>
> Who is right? Will it work or not?

Quick and dirty method:
1. Add new system name to existing SCDS and ACDS. Don't worry, it is nothing 
wrong to have non-present system names there.
2. Copy all *CDS to disk belonging to new system.
3. IPL the system.

Of course this is method for some migration. ACS routines, class definitions 
and library definitions will be moved. Is that what you want?
Otherwise there is another method, to start from scratch. ACS routines can be 
easily imported, class definitions - the only way I know is to re-define them 
manually.
BTW: some dummy SMS environment is delivered with ServerPac. I always start 
from that point. Then IPL with CPAC system name, then add my name to ACDS then 
reIPL with my system name. Then *CDS datasets can be imported (copied). Piece 
of cake.

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

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


CBT Tape Version 499 has been loaded

2020-05-19 Thread Sam Golob

Hi Folks,

    At www.cbttape.org we have loaded CBT Version 499.  Please enjoy. 
Remember to refer to the Updates Page first, in between version releases.


Sincerely,   Sam


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


Re: Creating new SMS environment in a monoplex

2020-05-19 Thread R.S.

W dniu 18.05.2020 o 20:36, Richards, Robert B. pisze:

It has been a few decades since I have created a new SMS environment.

Current environment is parallel sysplex replete with CFs and lots of lpars.

I am trying to create a simple SMS environment that will be part of a monoplex 
consisting on one lpar.

I did the following:


   1.  Defined the new SYSNAME into the base configuration in ISMF and 
activated same. D SMS verified it was defined and not active
   2.  A REPRO of the SCDS into a new SCDS dataset (Alter/newname to correct 
usercat)
   3.  Issued a SETSMS SAVEACDS(also using a SSA connector that I subsequently 
ALTER NEWNAME the new ACDS into a new usercat that is connected to a new 
mastercat)
   4.  Defined an empty COMMDS that I also performed an alter/newname to get 
the desired COMMDS dataset name.

My boss says the ACDS is aware of the original sysplex environment and my 
gyrations of trying to make the above work in a monoplex will not succeed.

Who is right? Will it work or not?


Quick and dirty method:
1. Add new system name to existing SCDS and ACDS. Don't worry, it is 
nothing wrong to have non-present system names there.

2. Copy all *CDS to disk belonging to new system.
3. IPL the system.

Of course this is method for some migration. ACS routines, class 
definitions and library definitions will be moved. Is that what you want?
Otherwise there is another method, to start from scratch. ACS routines 
can be easily imported, class definitions - the only way I know is to 
re-define them manually.
BTW: some dummy SMS environment is delivered with ServerPac. I always 
start from that point. Then IPL with CPAC system name, then add my name 
to ACDS then reIPL with my system name. Then *CDS datasets can be 
imported (copied). Piece of cake.


--
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: Does allocating an HFS or zFS erase all existing data?intervals formatted?

2020-05-19 Thread Seymour J Metz
Because Wikipedia would not consider that a reliable source. What I need is a 
published document that I can cite to justify the challenged footnote 

" 1 Not true for CMS file system[2] on a CMS minidisk, TSS VAM-formatted 
volume,[3] 
 z/OS Unix file systems[citation needed] or VSAM in IBM mainframes " 
to 
"As a general rule,[nb 1] formatting a disk by default leaves most if not 
all existing data
 on the disk medium; some or most of which might be recoverable with 
privileged[nb 2]
 or special tools.[4]"


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


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Mark Jacobs [0224d287a4b1-dmarc-requ...@listserv.ua.edu]
Sent: Tuesday, May 19, 2020 10:08 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Does allocating an HFS or zFS erase all existing data?intervals 
formatted?

Unless I'm totally off the mark here, why not go through this process (or 
something like it) and see for yourself.

1) Use an empty 3390 volume.
2) Allocate a single PS dataset that takes up the entire volume.
3) Use IEBDG to write a known value to each block in the dataset.
4) Delete the dataset.
5) Allocate HSF and zFS datasets on the volume.
6) DFDSS (or other tool) to print the track contents in the allocated space.
7) Review output.

Mark Jacobs


Sent from ProtonMail, Swiss-based encrypted email.

GPG Public Key - 
https://secure-web.cisco.com/1gFYwIxkr1KZghOPP0bmd9UCZ3A32F6aKyRlie071QEp6B8F4K5623W_ZThHbxX_9XjtAI51EmQ9VqQf6ftGgqa8RHkNUgQkupA2dcNYGPCDt6hjTWtXQmUgUhtrSHHZlbJlpusSRr-cqz27SDoB0auiltqFr6X0jamxG0gDa9X4vnUbwfQRrN6ZBsFsclp6TI8zlzKOCxB4jcXLIHe8sPvcS0QuUExDXarvaWIMKe46mi7YeFieyHxf_FaQL2FUshplNXeIwn-QQ6Tgt40GL3JTb9DGoVje-22LgV5w783cp7btfgseip0nl64JQdpJpKzZFs2RHMTAXLxouRfAahorTrMcGBxcZOG0gMEgbSf_8xgeOzCYJrDzc3VUIz3WRguaRh0vgG5kO5f2EK9iU-ZqFeQEK8_K8tIBrKpf0SBlIGosd0whdiKKOoUETBlSB/https%3A%2F%2Fapi.protonmail.ch%2Fpks%2Flookup%3Fop%3Dget%26search%3Dmarkjacobs%40protonmail.com

‐‐‐ Original Message ‐‐‐
On Tuesday, May 19, 2020 9:30 AM, Seymour J Metz  wrote:

> There is, or used to be, a common service used by VSAM and other components 
> for data with CI-like formatting, including PDSE. If it still exists then I 
> assume that it is also used for HFS. My prime concern was HFS and zFS, and I 
> don't know whether SPEED/RECOVERY applies to linear, which zFS is based on.
>
>
> --
>
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
> Mike Kerford-Byrnes [m...@hill-leys.com]
> Sent: Tuesday, May 19, 2020 8:11 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Does allocating an HFS or zFS erase all existing data?intervals 
> formatted?
>
> From various manuals - and a lot of time spent with VSAM...
>
> A VSAM file is DEFINEd with an amount of space. This space is managed by
> VSAM as a set of Control Areas (CAs). The maximum size of a CA is 1
> Cylinder, and the minimum is one track.
>
> Each CA contains a number of Control Intervals (CIs), of fixed length,
> determined at DEFINE time. The last 4 bytes of a CI (the CIDF) contain
> information as to the occupancy of the CI (amount of unused space and its
> offset). A CIDF containing all zeros is known as a Software End Of File or
> SEOF. The CIDF of an EMPTY CI shows (CISIZ - 4) bytes available at offset
> 0.
>
> Records are stored in the CI (left to right) along with control information
> (3-byte 'RDF' stored right to left).
>
> Linear Datasets are different. They do not have any control information in
> the (mandatory) 4K CIs which are employed to store the data. As far as I
> can deduce, the only connection to VSAM is that it provides the vehicle to
> read and write 4K blocks of data to and from a disk and a catalog structure
> in which to hold relevant data about the file - name, size, volser etc.
> Although I have used a linear Dataset in the past (1994!) I have not
> researched it in any detail.
>
> When a file is DEFINEd, nothing happens to the tracks. Only when the file
> is loaded does anything happen.
>
> What happens depends on the choice of SPEED/RECOVERY at DEFINE time and the
> type of VSAM file.
>
> SPEED
>
> When SPEED is specified, records are loaded into each control interval,
> along with the RDF, and the CIDF is updated as each record is loaded. This
> continues across all relevant CIs until the load is complete. At CLOSE (and
> only then), the SEOF is written and the Catalog will show a value in the
> High Used RBA field.
>
> For ESDS and RRDS, the SEOF is written in the CI FOLLOWING the last occupied
> CI. All remaining CIs

Re: SHARE annouce plans for an online SHARE was Re: Yechnical

2020-05-19 Thread Jonathan Quay
I loved SHARE, the (very) few times in my career I was allowed to attend.  
Seems I always had budget or membership constraints.  Hopefully one of the 
changes to come out of all this is a much easier and cheaper virtual presence 
for groups like this.  All the pundits say "the virus will change the way we 
work and interact permanently".  We'll see I guess.

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


Re: Does allocating an HFS or zFS erase all existing data?intervals formatted?

2020-05-19 Thread Mark Jacobs
Unless I'm totally off the mark here, why not go through this process (or 
something like it) and see for yourself.

1) Use an empty 3390 volume.
2) Allocate a single PS dataset that takes up the entire volume.
3) Use IEBDG to write a known value to each block in the dataset.
4) Delete the dataset.
5) Allocate HSF and zFS datasets on the volume.
6) DFDSS (or other tool) to print the track contents in the allocated space.
7) Review output.

Mark Jacobs


Sent from ProtonMail, Swiss-based encrypted email.

GPG Public Key - 
https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com

‐‐‐ Original Message ‐‐‐
On Tuesday, May 19, 2020 9:30 AM, Seymour J Metz  wrote:

> There is, or used to be, a common service used by VSAM and other components 
> for data with CI-like formatting, including PDSE. If it still exists then I 
> assume that it is also used for HFS. My prime concern was HFS and zFS, and I 
> don't know whether SPEED/RECOVERY applies to linear, which zFS is based on.
>
>
> --
>
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
> Mike Kerford-Byrnes [m...@hill-leys.com]
> Sent: Tuesday, May 19, 2020 8:11 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Does allocating an HFS or zFS erase all existing data?intervals 
> formatted?
>
> From various manuals - and a lot of time spent with VSAM...
>
> A VSAM file is DEFINEd with an amount of space. This space is managed by
> VSAM as a set of Control Areas (CAs). The maximum size of a CA is 1
> Cylinder, and the minimum is one track.
>
> Each CA contains a number of Control Intervals (CIs), of fixed length,
> determined at DEFINE time. The last 4 bytes of a CI (the CIDF) contain
> information as to the occupancy of the CI (amount of unused space and its
> offset). A CIDF containing all zeros is known as a Software End Of File or
> SEOF. The CIDF of an EMPTY CI shows (CISIZ - 4) bytes available at offset
> 0.
>
> Records are stored in the CI (left to right) along with control information
> (3-byte 'RDF' stored right to left).
>
> Linear Datasets are different. They do not have any control information in
> the (mandatory) 4K CIs which are employed to store the data. As far as I
> can deduce, the only connection to VSAM is that it provides the vehicle to
> read and write 4K blocks of data to and from a disk and a catalog structure
> in which to hold relevant data about the file - name, size, volser etc.
> Although I have used a linear Dataset in the past (1994!) I have not
> researched it in any detail.
>
> When a file is DEFINEd, nothing happens to the tracks. Only when the file
> is loaded does anything happen.
>
> What happens depends on the choice of SPEED/RECOVERY at DEFINE time and the
> type of VSAM file.
>
> SPEED
>
> When SPEED is specified, records are loaded into each control interval,
> along with the RDF, and the CIDF is updated as each record is loaded. This
> continues across all relevant CIs until the load is complete. At CLOSE (and
> only then), the SEOF is written and the Catalog will show a value in the
> High Used RBA field.
>
> For ESDS and RRDS, the SEOF is written in the CI FOLLOWING the last occupied
> CI. All remaining CIs in the current CA are also formatted as EMPTY.
>
> For a KSDS, all remaining CIs in the CA are formatted as EMPTY, and the
> first CI in the NEXT CA is also formatted as SEOF (assuming space is
> available). The HURBA reflects the last byte in the CA that contains loaded
> data.
>
> RECOVERY
>
> When RECOVERY is specified (or defaulted), each CA is preformatted
> immediately prior to its load.
>
> For both ESDS and RRDS, each CI in the CA is formatted with SEOF.
>
> For a KSDS, All CIs in the CA are formatted as EMPTY and the first CI of the
> NEXT CA is also formatted as a SEOF (again assuming space is available).
>
> In all cases, the load of that CA proceeds updating each CI in turn.
>
> CLOSE will update the HURBA as per SPEED.
>
> The net of this is that, in the case of RECOVERY, if the load fails part-way
> through, there is a predictable format in the file structure such that a
> 'resume load' can be executed (that is if you have programmed one to start
> with!). There will always be a SEOF which identifies the last point at
> which data was loaded. This is identified when a subsequent OPEN, having
> detected a 'failed CLOSE', invokes the VERIFY function, which locates the
> SEOF, updates the catalog and then resumes the OPEN process with a 'clean'
> catalog. In the case of SPEED, there is no such support and you have to go
> back to the beginning and rerun. Although RECOVERY is the default, IBM
>

Re: tcpip or telnet

2020-05-19 Thread PINION, RICHARD W.
This company used to have a trial copy of their software available for download.

https://www.servicepilot.com/en/application-flow/mainframe/

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Mike Wawiorko
Sent: Tuesday, May 19, 2020 9:33 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: tcpip or telnet

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

History

You may find this SMF record interesting for historical detail. It relies on 
configuring MONITORGROUP.
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.halx001/serversna.htm

TN3270E Telnet server round trip performance section. This section is optional 
and is present when performance data is being collected for this connection as 
a result of a MONITORGROUP being mapped to this connection.


NMI

For (near) real time I guess you'd need a network monitor. There are several 
marketed that use the z/OS TCPIP stack NMI (Network Management Interface) to 
give detail similar to the SMF record.

Mike Wawiorko

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Shelia Chalk
Sent: 19 May 2020 13:52
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: tcpip or telnet


This mail originated from outside our organisation - sch...@trustmark.com

I don't know were to start, but i will try to explain what i am looking for... 
tcpip i am looking batch job or command that will produce a report to see if i 
have got any connections very slow or over loaded.. if there is such a thing. i 
want to find any connection that has a delay and a report gives me that 
information..

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

This e-mail and any attachments are confidential and intended solely for the 
addressee and may also be privileged or exempt from disclosure under applicable 
law. If you are not the addressee, or have received this e-mail in error, 
please notify the sender immediately, delete it from your system and do not 
copy, disclose or otherwise act upon any part of this e-mail or its attachments.
Internet communications are not guaranteed to be secure or virus-free. The 
Barclays Group does not accept responsibility for any loss arising from 
unauthorised access to, or interference with, any Internet communications by 
any third party, or from the transmission of any viruses. Replies to this 
e-mail may be monitored by the Barclays Group for operational or business 
reasons.
Any opinion or other information in this e-mail or its attachments that does 
not relate to the business of the Barclays Group is personal to the sender and 
is not given or endorsed by the Barclays Group.
Barclays Execution Services Limited provides support and administrative 
services across Barclays group. Barclays Execution Services Limited is an 
appointed representative of Barclays Bank UK plc, Barclays Bank plc and 
Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays Bank 
plc are authorised by the Prudential Regulation Authority and regulated by the 
Financial Conduct Authority and the Prudential Regulation Authority. Clydesdale 
Financial Services Limited is authorised and regulated by the Financial Conduct 
Authority.

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


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


Re: tcpip or telnet

2020-05-19 Thread Mike Wawiorko
History

You may find this SMF record interesting for historical detail. It relies on 
configuring MONITORGROUP.
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.halx001/serversna.htm

TN3270E Telnet server round trip performance section. This section is optional 
and is present when performance data is being collected for this connection as 
a result of a MONITORGROUP being mapped to this connection.


NMI

For (near) real time I guess you'd need a network monitor. There are several 
marketed that use the z/OS TCPIP stack NMI (Network Management Interface) to 
give detail similar to the SMF record.

Mike Wawiorko   

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Shelia Chalk
Sent: 19 May 2020 13:52
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: tcpip or telnet


This mail originated from outside our organisation - sch...@trustmark.com

I don't know were to start, but i will try to explain what i am looking for... 
tcpip i am looking batch job or command that will produce a report to see if i 
have got any connections very slow or over loaded.. if there is such a thing. i 
want to find any connection that has a delay and a report gives me that 
information..

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

This e-mail and any attachments are confidential and intended solely for the 
addressee and may also be privileged or exempt from disclosure under applicable 
law. If you are not the addressee, or have received this e-mail in error, 
please notify the sender immediately, delete it from your system and do not 
copy, disclose or otherwise act upon any part of this e-mail or its attachments.
Internet communications are not guaranteed to be secure or virus-free. The 
Barclays Group does not accept responsibility for any loss arising from 
unauthorised access to, or interference with, any Internet communications by 
any third party, or from the transmission of any viruses. Replies to this 
e-mail may be monitored by the Barclays Group for operational or business 
reasons.
Any opinion or other information in this e-mail or its attachments that does 
not relate to the business of the Barclays Group is personal to the sender and 
is not given or endorsed by the Barclays Group.
Barclays Execution Services Limited provides support and administrative 
services across Barclays group. Barclays Execution Services Limited is an 
appointed representative of Barclays Bank UK plc, Barclays Bank plc and 
Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays Bank 
plc are authorised by the Prudential Regulation Authority and regulated by the 
Financial Conduct Authority and the Prudential Regulation Authority. Clydesdale 
Financial Services Limited is authorised and regulated by the Financial Conduct 
Authority.

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


Re: Does allocating an HFS or zFS erase all existing data?intervals formatted?

2020-05-19 Thread Seymour J Metz
There is, or used to be, a common service used by VSAM and other components for 
data with CI-like formatting, including PDSE. If it still exists then I assume 
that it is also used for HFS. My prime concern was HFS and zFS, and I don't 
know whether SPEED/RECOVERY applies to linear, which zFS is based on.


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


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
Mike Kerford-Byrnes [m...@hill-leys.com]
Sent: Tuesday, May 19, 2020 8:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Does allocating an HFS or zFS erase all existing data?intervals 
formatted?

>From various manuals - and a lot of time spent with VSAM...



A VSAM file is DEFINEd with an amount of space.  This space is managed by
VSAM as a set of Control Areas (CAs).  The maximum size of a CA is 1
Cylinder, and the minimum is one track.



Each CA contains a number of Control Intervals (CIs), of fixed length,
determined at DEFINE time.  The last 4 bytes of a CI (the CIDF) contain
information as to the occupancy of the CI (amount of unused space and its
offset).  A CIDF containing all zeros is known as a Software End Of File or
SEOF.  The CIDF of an EMPTY CI shows (CISIZ - 4) bytes available at offset
0.



Records are stored in the CI (left to right) along with control information
(3-byte 'RDF' stored right to left).



Linear Datasets are different.  They do not have any control information in
the (mandatory) 4K CIs which are employed to store the data.  As far as I
can deduce, the only connection to VSAM is that it provides the vehicle to
read and write 4K blocks of data to and from a disk and a catalog structure
in which to hold relevant data about the file - name, size, volser etc.
Although I have used a linear Dataset in the past (1994!) I have not
researched it in any detail.



When a file is DEFINEd, nothing happens to the tracks.  Only when the file
is loaded does anything happen.

What happens depends on the choice of SPEED/RECOVERY at DEFINE time and the
type of VSAM file.



SPEED



When SPEED is specified, records are loaded into each control interval,
along with the RDF, and the CIDF is updated as each record is loaded.  This
continues across all relevant CIs until the load is complete.  At CLOSE (and
only then), the SEOF is written and the Catalog will show a value in the
High Used RBA field.



For ESDS and RRDS, the SEOF is written in the CI FOLLOWING the last occupied
CI.  All remaining CIs in the current CA are also formatted as EMPTY.



For a KSDS, all remaining CIs in the CA are formatted as EMPTY, and the
first CI in the NEXT CA is also formatted as SEOF (assuming space is
available).  The HURBA reflects the last byte in the CA that contains loaded
data.



RECOVERY



When RECOVERY is specified (or defaulted), each CA is preformatted
immediately prior to its load.



For both ESDS and RRDS, each CI in the CA is formatted with SEOF.



For a KSDS, All CIs in the CA are formatted as EMPTY and the first CI of the
NEXT CA is also formatted as a SEOF (again assuming space is available).



In all cases, the load of that CA proceeds updating each CI in turn.



CLOSE will update the HURBA as per SPEED.



The net of this is that, in the case of RECOVERY, if the load fails part-way
through, there is a predictable format in the file structure such that a
'resume load' can be executed (that is if you have programmed one  to start
with!).  There will always be a SEOF which identifies the last point at
which data was loaded.   This is identified when a subsequent OPEN, having
detected a 'failed CLOSE', invokes the VERIFY function, which locates the
SEOF, updates the catalog and then resumes the OPEN process with a 'clean'
catalog.  In the case of SPEED, there is no such support and you have to go
back to the beginning and rerun.  Although RECOVERY is the default, IBM
recommend SPEED, since it is obviously a faster option.



There is one 'gotcha' in this story.  Once a file has been loaded (I.e. at
least one record written, followed by a successful CLOSE), RECOVERY is
operative, irrespective of the SPEED/RECOVERY option chosen at DEFINE time.
So don't do what I have seen a couple of times - Open, load 1 control
record, Close, followed by Open, load thousands of records, Close - under
the misconception that SPEED is in effect throughout.



Mike Kerford-Byrnes




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

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


AW: tcpip or telnet

2020-05-19 Thread Mike Beer
Hi
In a linux environment you could use tools like ping and traceroute.
You would see, if your target is reachable and how fast the connection is 
(latency between nodes).
The availability (and names) of such (basic) tools depend on your operating 
system.

e.g. some z/OS info:
https://www.ibm.com/support/knowledgecenter/zosbasics/com.ibm.zos.znetwork/znetwork_344.htm

Using PING and REXX you could easily write such a reporting tool that scans 
your target IP addresses.

Best regards
Mike


-Ursprüngliche Nachricht-
Von: IBM Mainframe Discussion List  Im Auftrag von 
Shelia Chalk
Gesendet: Tuesday, May 19, 2020 14:52
An: IBM-MAIN@LISTSERV.UA.EDU
Betreff: tcpip or telnet

I don't know were to start, but i will try to explain what i am looking for... 
tcpip i am looking batch job or command that will produce a report to see if i 
have got any connections very slow or over loaded.. if there is such a thing. i 
want to find any connection that has a delay and a report gives me that 
information..

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

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


tcpip or telnet

2020-05-19 Thread Shelia Chalk
I don't know were to start, but i will try to explain what i am looking for... 
tcpip i am looking batch job or command that will produce a report to see if i 
have got any connections very slow or over loaded.. if there is such a thing. i 
want to find any connection that has a delay and a report gives me that 
information..

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


Re: Creating new SMS environment in a monoplex

2020-05-19 Thread Carmen Vitullo
your welcome Bob, yes please let me (us) know 


Carmen Vitullo 

- Original Message -

From: "Robert B. Richards" <01c91f408b9e-dmarc-requ...@listserv.ua.edu> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Monday, May 18, 2020 2:27:27 PM 
Subject: Re: Creating new SMS environment in a monoplex 

Thanks Carmen. I'll post the results when I try an IPL of that new system and 
SMS starts up 

-Original Message- 
From: IBM Mainframe Discussion List  On Behalf Of 
Carmen Vitullo 
Sent: Monday, May 18, 2020 3:05 PM 
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: Creating new SMS environment in a monoplex 

Hi Bob, been a while for me also, but in my current sysplex I have systems 
defined that no longer exist, my ACS routines do not check for these systems. 
my base configuration has 4 systems in the plex, only 3 exists, not sure this 
helps you but I think you are on the right track 



Carmen Vitullo 

- Original Message - 

From: "Robert B. Richards" <01c91f408b9e-dmarc-requ...@listserv.ua.edu> 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Monday, May 18, 2020 1:36:29 PM 
Subject: Creating new SMS environment in a monoplex 

It has been a few decades since I have created a new SMS environment. 

Current environment is parallel sysplex replete with CFs and lots of lpars. 

I am trying to create a simple SMS environment that will be part of a monoplex 
consisting on one lpar. 

I did the following: 


  1.  Defined the new SYSNAME into the base configuration in ISMF and activated 
same. D SMS verified it was defined and not active 
  2.  A REPRO of the SCDS into a new SCDS dataset (Alter/newname to correct 
usercat) 
  3.  Issued a SETSMS SAVEACDS(also using a SSA connector that I subsequently 
ALTER NEWNAME the new ACDS into a new usercat that is connected to a new 
mastercat) 
  4.  Defined an empty COMMDS that I also performed an alter/newname to get the 
desired COMMDS dataset name. 

My boss says the ACDS is aware of the original sysplex environment and my 
gyrations of trying to make the above work in a monoplex will not succeed. 

Who is right? Will it work or not? 

Bob 


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


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

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


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


Re: Does allocating an HFS or zFS erase all existing data?intervals formatted?

2020-05-19 Thread Mike Kerford-Byrnes
>From various manuals - and a lot of time spent with VSAM...

 

A VSAM file is DEFINEd with an amount of space.  This space is managed by
VSAM as a set of Control Areas (CAs).  The maximum size of a CA is 1
Cylinder, and the minimum is one track.

 

Each CA contains a number of Control Intervals (CIs), of fixed length,
determined at DEFINE time.  The last 4 bytes of a CI (the CIDF) contain
information as to the occupancy of the CI (amount of unused space and its
offset).  A CIDF containing all zeros is known as a Software End Of File or
SEOF.  The CIDF of an EMPTY CI shows (CISIZ - 4) bytes available at offset
0. 

 

Records are stored in the CI (left to right) along with control information
(3-byte 'RDF' stored right to left).

 

Linear Datasets are different.  They do not have any control information in
the (mandatory) 4K CIs which are employed to store the data.  As far as I
can deduce, the only connection to VSAM is that it provides the vehicle to
read and write 4K blocks of data to and from a disk and a catalog structure
in which to hold relevant data about the file - name, size, volser etc.
Although I have used a linear Dataset in the past (1994!) I have not
researched it in any detail. 

 

When a file is DEFINEd, nothing happens to the tracks.  Only when the file
is loaded does anything happen.

What happens depends on the choice of SPEED/RECOVERY at DEFINE time and the
type of VSAM file. 

 

SPEED

 

When SPEED is specified, records are loaded into each control interval,
along with the RDF, and the CIDF is updated as each record is loaded.  This
continues across all relevant CIs until the load is complete.  At CLOSE (and
only then), the SEOF is written and the Catalog will show a value in the
High Used RBA field. 

 

For ESDS and RRDS, the SEOF is written in the CI FOLLOWING the last occupied
CI.  All remaining CIs in the current CA are also formatted as EMPTY.

 

For a KSDS, all remaining CIs in the CA are formatted as EMPTY, and the
first CI in the NEXT CA is also formatted as SEOF (assuming space is
available).  The HURBA reflects the last byte in the CA that contains loaded
data.  

 

RECOVERY

 

When RECOVERY is specified (or defaulted), each CA is preformatted
immediately prior to its load.

 

For both ESDS and RRDS, each CI in the CA is formatted with SEOF.  

 

For a KSDS, All CIs in the CA are formatted as EMPTY and the first CI of the
NEXT CA is also formatted as a SEOF (again assuming space is available).

 

In all cases, the load of that CA proceeds updating each CI in turn.

 

CLOSE will update the HURBA as per SPEED.

 

The net of this is that, in the case of RECOVERY, if the load fails part-way
through, there is a predictable format in the file structure such that a
'resume load' can be executed (that is if you have programmed one  to start
with!).  There will always be a SEOF which identifies the last point at
which data was loaded.   This is identified when a subsequent OPEN, having
detected a 'failed CLOSE', invokes the VERIFY function, which locates the
SEOF, updates the catalog and then resumes the OPEN process with a 'clean'
catalog.  In the case of SPEED, there is no such support and you have to go
back to the beginning and rerun.  Although RECOVERY is the default, IBM
recommend SPEED, since it is obviously a faster option. 

 

There is one 'gotcha' in this story.  Once a file has been loaded (I.e. at
least one record written, followed by a successful CLOSE), RECOVERY is
operative, irrespective of the SPEED/RECOVERY option chosen at DEFINE time.
So don't do what I have seen a couple of times - Open, load 1 control
record, Close, followed by Open, load thousands of records, Close - under
the misconception that SPEED is in effect throughout. 

 

Mike Kerford-Byrnes 

 


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