Re: System check stopped state - what is it?

[Vernooij, CP (ITOPT1) - KLM]

Yes, I saw it's not a wait state. A check stop is the result of a hardware 
malfunctioning. Do a find on 'check stop' (not stopped) in POP. Maybe you can 
find the explanation of the 0C, possibly a bit-combination i.s.o. a value. 
Otherwise, you might have to consult the z13 manual for its specific check stop 
reasons.

Kees.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of R.S.
Sent: 22 January, 2016 16:02
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: System check stopped state - what is it?

Unfortunately no
HW message: A logically partitioned mode event occurred. Select Details 
for information.
Details: Logical partition LPAR01 is in the system check stopped state. 
Reason code = 0C.

Note, it's not wait state, just "system check stopped state".
I tried to use google, searched PoP and some other sources with no effect.

I believe it is documented, but where???

Regards
-- 
Radoslaw Skorupka
Lodz, Poland






W dniu 2016-01-22 o 15:51, Vernooij, CP (ITOPT1) - KLM pisze:
> No messges id?
> POP has some information about machine-checks and check-stop conditions, but 
> I couldn't find a 0C quickly.
>
> Kees.
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of R.S.
> Sent: 22 January, 2016 15:35
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: System check stopped state - what is it?
>
> I tried to perform LOAD on some LPAR.
> I've got the following message:
>
> Logical partition LPAR01 is in the system check stopped state. Reason
> code = 0C.
>
> Where to find the meaning of the code?
>
>
> It is z13 machine.
>




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

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

mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
www.mBank.pl, e-mail: kont...@mbank.pl
Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru 
Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. 
Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości 
wpłacony) wynosi 168.955.696 złotych.


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

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

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



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

Re: Compile error

[Gibney, David Allen,Jr]

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Mike Schwab
> Sent: Friday, January 22, 2016 12:32 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Compile error
> 
> On Fri, Jan 22, 2016 at 11:54 AM, Gibney, David Allen,Jr 
> wrote:
> > I've never worked with JES3. What does it offer in "disk and tape control"
> that DFSMS doesn't? Or, are we talking a different kind of control?
> 
> It doesn't start until the dataset names / tape volumes are not in use and
> there is sufficient free space on disk.  JES2 would start the job then wait 
> for
> them to be available.  Or the job could abend for lack of space.
> 

So, still scheduling, not really DASD or TAPE management.

> --
> Mike A Schwab, Springfield IL USA
> Where do Forest Rangers go to get away from it all?
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN

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

Identifying creator of SMF records

[Field, Alan]

Is there a way to identify what is creating user written SMF records?

We have 210s, 230s and 254s that we can't identify the source.

We've dumped the records and looked at them. Some give hints (e.g. the 230s 
look like perhaps CA OpsMVS, the 254s perhaps something related to SAF).

TIA

Alan


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

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

Re: Is there a source for detailed, instruction-level performance info?

[Frank Swarbrick]

I'm no assembler expert, but how about
L R15,COUNTER
AFI   R15,1
STR15,COUNTER

> Date: Fri, 22 Jan 2016 14:14:49 -0500
> From: i...@panix.com
> Subject: Re: Is there a source for detailed, instruction-level performance 
> info?
> To: IBM-MAIN@LISTSERV.UA.EDU
> 
> In article <000401d140df$6f05a2a0$4d10e7e0$@att.net> Skip wrote:
> 
> > As a newbie, I got curious about the relative speed of these strategies:
> >
> > 1. L R15, COUNTER
> > 2. A R15,=F(+1)
> > 3. ST R15, COUNTER
> >
> > 1. L R15, COUNTER
> > 2. LA R15,1(,R15) 
> > 3. ST R15, COUNTER
> >
> > I asked my manager, who encouraged me to delve into the manual Shmuel cites.
> > I decided that LA was faster because there was no storage access. The
> > program ran like a banshee. It ran so fast that it was used to benchmark new
> > hardware. Really!
> >
> > It wasn't till later that I pondered a basic flaw. As written, the program
> > could not handle a counter greater than 16M because it ran in 24 bit mode.
> > This was before XA. At the time I wrote it, the data base was comfortably
> > within that limit, but over time, long after I had moved on, I (still)
> > wonder if the application survived and if any counter ever hit the limit.
> > Moral: whether or not size matters, speed is certainly not a simple metric. 
> 
>L R15,COUNTER
>BCTR  R15,0
>STR15,COUNTER
> 
> gives a 2^31 limit, 2^32 if some care is taken when printing the totals, at
> speed comparable to LA.
> 
> --
> 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: Compile error

[Mike Schwab]

On Fri, Jan 22, 2016 at 11:54 AM, Gibney, David Allen,Jr  wrote:
> I've never worked with JES3. What does it offer in "disk and tape control" 
> that DFSMS doesn't? Or, are we talking a different kind of control?

It doesn't start until the dataset names / tape volumes are not in use
and there is sufficient free space on disk.  JES2 would start the job
then wait for them to be available.  Or the job could abend for lack
of space.

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

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

Re: Is there a source for detailed, instruction-level performance info?

[Frank Swarbrick]

Or dare I suggest:
ASI  COUNTER,1

> Date: Fri, 22 Jan 2016 14:30:02 -0700
> From: frank.swarbr...@outlook.com
> Subject: Re: Is there a source for detailed, instruction-level performance 
> info?
> To: IBM-MAIN@LISTSERV.UA.EDU
> 
> I'm no assembler expert, but how about
> L R15,COUNTER
> AFI   R15,1
> STR15,COUNTER
> 
> > Date: Fri, 22 Jan 2016 14:14:49 -0500
> > From: i...@panix.com
> > Subject: Re: Is there a source for detailed, instruction-level performance 
> > info?
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > 
> > In article <000401d140df$6f05a2a0$4d10e7e0$@att.net> Skip wrote:
> > 
> > > As a newbie, I got curious about the relative speed of these strategies:
> > >
> > > 1. L R15, COUNTER
> > > 2. A R15,=F(+1)
> > > 3. ST R15, COUNTER
> > >
> > > 1. L R15, COUNTER
> > > 2. LA R15,1(,R15) 
> > > 3. ST R15, COUNTER
> > >
> > > I asked my manager, who encouraged me to delve into the manual Shmuel 
> > > cites.
> > > I decided that LA was faster because there was no storage access. The
> > > program ran like a banshee. It ran so fast that it was used to benchmark 
> > > new
> > > hardware. Really!
> > >
> > > It wasn't till later that I pondered a basic flaw. As written, the program
> > > could not handle a counter greater than 16M because it ran in 24 bit mode.
> > > This was before XA. At the time I wrote it, the data base was comfortably
> > > within that limit, but over time, long after I had moved on, I (still)
> > > wonder if the application survived and if any counter ever hit the limit.
> > > Moral: whether or not size matters, speed is certainly not a simple 
> > > metric. 
> > 
> >L R15,COUNTER
> >BCTR  R15,0
> >STR15,COUNTER
> > 
> > gives a 2^31 limit, 2^32 if some care is taken when printing the totals, at
> > speed comparable to LA.
> > 
> > --
> > 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

zEDC

[Phillips, Thomas]

Is anyone using the new zEDC cards in a production environment?  We are running 
z13's with z/OS 2.1.

Feel free to contact me offline, if you'd like.

Thanks,
Tom Phillips
Principal Financial Group

-Message Disclaimer-

This e-mail message is intended only for the use of the individual or entity to 
which it is addressed, and may contain information that is privileged, 
confidential and exempt from disclosure under applicable law. If you are not 
the intended recipient, any dissemination, distribution or copying of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by reply email to conn...@principal.com 
and delete or destroy all copies of the original message and attachments 
thereto. Email sent to or from the Principal Financial Group or any of its 
member companies may be retained as required by law or regulation.

Nothing in this message is intended to constitute an Electronic signature for 
purposes of the Uniform Electronic Transactions Act (UETA) or the Electronic 
Signatures in Global and National Commerce Act ("E-Sign") unless a specific 
statement to the contrary is included in this message.

If you no longer wish to receive any further solicitation from the Principal 
Financial Group you may unsubscribe at 
https://www.principal.com/do-not-contact-form any time.

If you are a Canadian resident and no longer wish to receive commercial 
electronic messages you may unsubscribe at 
https://www.principal.com/do-not-email-request-canadian-residents any time.

--
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 source for detailed, instruction-level performance info?

[Charles Mills]

Depending on the newness of your hardware.

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Frank Swarbrick
Sent: Friday, January 22, 2016 1:32 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Is there a source for detailed, instruction-level performance
info?

Or dare I suggest:
ASI  COUNTER,1

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

Re: Identifying creator of SMF records

[Charles Mills]

230 is probably ACF2 if that is a possibility.
210 might be Voltage if that is a possibility.

http://www.watsonwalker.com/SMFreference.pdf 

If you turn those types off in SMFPRMxx you may get an error message from
the component that is trying to write them.

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Field, Alan
Sent: Friday, January 22, 2016 1:31 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Identifying creator of SMF records

Is there a way to identify what is creating user written SMF records?

We have 210s, 230s and 254s that we can't identify the source.

We've dumped the records and looked at them. Some give hints (e.g. the 230s
look like perhaps CA OpsMVS, the 254s perhaps something related to SAF).

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

Re: Man Versus System

[Phil Smith III]

John McKown wrote, re TPF:

>I worked at Braniff Airways before it went under. The reservation system

>ran ACP on a 2 Meg 3033. The thing would IPL in about 5 seconds. The ACP

>systems people were a bit strange. They had the source and modified it. I

>remember the CE complaining that the ACP attached tapes (3420s) would just

>die with "no warnings at all" whereas the MVT (yes MVT on a 3033) and, a

>bit later MVS and VM would show temp errors. The ACP people then told the

>CE that they had removed all logging of temporary errors to speed up

>processing. Not just on the tapes, but on the 3344 disks as well. IIRC, the

>3344s on ACP actually used "software duplexing" for reliability.

 

My favorite TPF story, from Sabre, circa 1988:

Someone started a TPF transaction without proper testing, and it clipped
something like 1,000 packs. MVS and TPF were quite unhappy about it.

 

While the MVS and TPF guys were moaning, Mike Roegner (now retired) quietly
went over to the VM system and wrote a small Rexx program to attach, ICKDSF
(or whatever the equivalent was-this would have been pre-XA, and I forget!),
and detach, and started relabeling the packs.

 

Meanwhile, they were down for several hours, at a reported cost of
$20,000/minute. And of course neither Mike nor VM got the credit they
deserved for saving the day. The outage did make ComputerWorld, however. (Of
course it did-would ComputerWorld ever forego the opportunity to run a
negative story?)

 

.phsiii


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

Re: Man Versus System

[Anne & Lynn Wheeler]

john.archie.mck...@gmail.com (John McKown) writes:
> ​Descended from ACP (Airline Control Program).
> https://en.wikipedia.org/wiki/IBM_Airline_Control_Program​
>
> I worked at Braniff Airways before it went under. The reservation system
> ran ACP on a 2 Meg 3033. The thing would IPL in about 5 seconds. The ACP
> systems people were a bit strange. They had the source and modified it. I
> remember the CE complaining that the ACP attached tapes (3420s) would just
> die with "no warnings at all" whereas the MVT (yes MVT on a 3033) and, a
> bit later MVS and VM would show temp errors. The ACP people then told the
> CE that they had removed all logging of temporary errors to speed up
> processing. Not just on the tapes, but on the 3344 disks as well. IIRC, the
> 3344s on ACP actually used "software duplexing" for reliability.

there was big problem with 3081 ... which originally was going to be
multiprocessor only ... and ACP/TPF didn't have multiprocessor support
(they were afraid that the whole market would move to clone processors
which were building newer single processor machines). An an interim they
shipped some number of releases of VM370 with very unnatural things done
to it specifically for running ACP/TPF on multiprocessors (but degraded
performance for all other customers). Eventually they shipped 3083 ...
which was a 3081 box with one of the processors removed (minor trivia,
simplest would be to remove the 2nd processor which was in the middle of
the box ... but that would have made the box dangerously top-heavy, they
had to rewrire "processor 0" to processor in the middle and remove the
processor at the top of the box). other issues with 308x
... highlighting that it was warmed over FS technology
http://www.jfsowa.com/computer/memo125.htm

later in the 80s, my wife did temporary stint as chief architect for
Amedeus (euro res system based on old eastern "system one") ... the
communication group got her replaced because she backed x.25 (instead of
sna/vtam) ... it didn't do them much good because amedeus went with x.25
anyway.

later in the mid-90s, we were asked to look at re-engineering some of
the largest airline res system in the world ... starting with ROUTES
(about 25% of total mainframe processing load) addressing the ten
impossible things that they couldn't do. I went away and two months
later came back with totally different ROUTES implementation that ran
about hundred times faster and did all ten impossible things
... including ten RS/6000 990s being able to handle every ROUTES
transaction for every airline in the world. The issue was much of
ACP/TPF implementation was dictated by technology trade-offs made in the
60s ... it was possible to start from scratch 30yrs later and make
totally different trade-offs (and a decade later, cellphone processors
had processing capacity of those ten 990s).

It was fun because they provided me with tape of the full OAG ...
including record for every scheduled airline flt in the world.

-- 
virtualization experience starting Jan1968, online at home since Mar1970

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

Re: Compile error

[Rugen, Len]

I ran OS/VS1 on a 4341 and later I think on a 4381.  We also ran VM, OS/VS1 had 
a VM "Assist" mode where it didn't page, but let VM page for it.  I think 
OS/VS1 ran JES, just JES, no 2 or 3 after it, but it looked a lot like JES2.  

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

Re: Compile error

[Pommier, Rex]

I'm guessing it comes from the same place that causes people to pronounce CICS 
"kicks".  IIRC, DL1 is actually morphed from DL/1 which morphed from DL/I which 
is the acronym for Data Language/Interface which is part of IMS, is it not?  

Rex

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of McCabe, Ron
Sent: Friday, January 22, 2016 11:40 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Compile error

So where does DL1 fit in?

Ron McCabe
Mutual of Enumclaw

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Pommier, Rex
Sent: Friday, January 22, 2016 9:05 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Compile error

Probably just an old fairy tale, but I was told long ago that DB2 came about as 
a name because IBM already had IMS so the 2 in DB2 was to distinguish it as 
being IBM's second DBMS offering.

Rex

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Skip Robinson
Sent: Friday, January 22, 2016 10:51 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Compile error

The name 'DB2' seems to have followed the 1980s tradition of what I call 'name 
bloat', the practice of inflating a moniker in one way or another to make a 
product look more mature or more elegant. The paragon in my mind was dBASE II 
from Ashton-Tate. There never was a plain old dBASE. The roman numeral was 
added from the get-go to make the product seem new and improved.
Moreover, there was never an 'Ashton'. That name was invented because, gosh 
darn it, it sounded good hyphenated with Tate, a real person.

Before DB2 there was precedent for name bloat within IBM. There never was a 
plain old 'JES'. The product emerged from the cocoon as JES2. There had been a 
predecessor product called 'HASP', which may or may not have been an acronym 
for Houston Automatic Spooling Priority, but the name 'J-E-S' was born complete 
with suffix.

Meanwhile there did emerge a 'JES3', but it was not an evolutionary descendant 
of JES2. Both products have coexisted, albeit uneasily, for decades. We used to 
imagine a JES5 or JES6 (depending on one's arithmetic
proclivity) that would somehow combine the best features of both products, but 
it's almost certainly DOA. Likewise, the prospects for a 'DB3' are as dim as a 
distant star.

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
jo.skip.robin...@att.net
jo.skip.robin...@gmail.com

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

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Confidentiality Notice: This e- mail and all attachments may contain 
CONFIDENTIAL information and are meant solely for the intended recipient. It 
may contain controlled, privileged, or proprietary information that is 
protected under applicable law and shall not be disclosed to any unauthorized 
third party. If you are not the intended recipient, you are hereby notified 
that any unauthorized review, action, disclosure, distribution, or reproduction 
of any information contained in this e- mail and any attachments is strictly 
PROHIBITED. If you received this e- mail in error, please reply to the sender 
immediately stating that this transmission was misdirected, and delete or 
destroy all electronic and paper copies of this e-mail and attachments without 
disclosing the contents. This e- mail does not grant or assign rights of 
ownership in the proprietary subject matter herein, nor shall it be construed 
as a joint venture, partnership, teaming agreement, or any other formal 
business relationship.

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


The information contained in this message is confidential, protected from 
disclosure and may be legally privileged.  If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 

Re: Compile error

[Anne & Lynn Wheeler]

jo.skip.robin...@att.net (Skip Robinson) writes:
> The name 'DB2' seems to have followed the 1980s tradition of what I call
> 'name bloat', the practice of inflating a moniker in one way or another to
> make a product look more mature or more elegant. The paragon in my mind was
> dBASE II from Ashton-Tate. There never was a plain old dBASE. The roman
> numeral was added from the get-go to make the product seem new and improved.
> Moreover, there was never an 'Ashton'. That name was invented because, gosh
> darn it, it sounded good hyphenated with Tate, a real person. 
>
> Before DB2 there was precedent for name bloat within IBM. There never was a
> plain old 'JES'. The product emerged from the cocoon as JES2. There had been
> a predecessor product called 'HASP', which may or may not have been an
> acronym for Houston Automatic Spooling Priority, but the name 'J-E-S' was
> born complete with suffix. 
>
> Meanwhile there did emerge a 'JES3', but it was not an evolutionary
> descendant of JES2. Both products have coexisted, albeit uneasily, for
> decades. We used to imagine a JES5 or JES6 (depending on one's arithmetic
> proclivity) that would somehow combine the best features of both products,
> but it's almost certainly DOA. Likewise, the prospects for a 'DB3' are as
> dim as a distant star.

note that VS1 had JES1 (Job Entry Subsystem 1)
https://en.wikipedia.org/wiki/OS/VS1

The official names were OS/VS1 and OS/VS2 ... so JES2 originally may
have originally been to designate it was for OS/VS2.

Long ago and far away, my wife was in the GBURG JES group and was part
of the catchers for ASP turning into JES3. She was then co-author of
JESUS (JES UNIFIED SYSTEM) document ... which merged the features in
JES2 and JES3 that respective customers couldn't live w/o ...  for
various reasons never saw the light of day.

A Fascinating History of JES2
http://www.share.org/p/bl/et/blogid=9=238

For the truth we must go back to the mid 1960's.  IBM's OS/360 was in
trouble.  The spooling (wonder where that name came from) support was
slow and the overhead was high.  Many programming groups independently
attacked the problem.  ASP, loosely based upon the tightly coupled IBM
7090/7094 DCS, held the lead in the OS/360 spooling sweepstakes.  ASP's
need for at least two CPU's fit well with IBM Marketing's plans for the
System/360.  Meanwhile, a group of IBM SE's, located in Houston,
developed a different product of which they were justifiably proud.
They wanted to popularize it, as they correctly suspected it would be
the balm for OS/360 users, increasing the usability and popularity of
the operating system, and, not incidentally, furthering their careers.
All they needed was the right name!  A name which was easy to remember,
a name which would draw attention to their product, and a name to
distract from the ASP publicity.  That name was Half-ASP, or HASP.
Naturally, if HASP and ASP were products of two different companies, the
FTC would have stepped in to stop such a predatory product name.
Regulatory action was prevented, however, because IBM is "one big happy
family", believed by many to be larger than the Government.

... snip ...

of course officially, the "H" stands for "Houston"
https://en.wikipedia.org/wiki/Houston_Automatic_Spooling_Priority

then my wife was con'ed into going to POK to be responsible for
loosely-coupled architecture ... where she "peer-coupled shared data
architecture" ... which saw very little uptake (except for IMS
hot-standby) until SYSPLEX & Parallel SYSPLEX ... contributing to her
not remaining long in POK (along with the ongoing periodic battles with
the communication group trying to force her into using SNA/VTAM for
loosely-coupled operation). some past posts
http://www.garlic.com/~lynn/submain.html#shareddata

as undergraduate in the 60s, I got to make a lot of HASP modifications
(I had also been hired fulltime by the university to be responsible for
production mainframe systems) ... including implementing terminal
support and conversational editor in HASP for a form of CRJE.
https://en.wikipedia.org/wiki/Remote_job_entry

DB2 may have been because some had hopes that the official new DBMS
"EAGLE" might still be able to rise from its ashes ... or it was to
designate the OS/VS2 (aka MVS) version of System/R as opposed to the
earlier SQL/DS version of System/R (that ran on VM370, VS1, DOS/VSE).

trivia: one of the problems with the System/R tech transfer to Endicott
for SQL/DS ... was that several enhancements to vm370 had been made to
make System/R much more efficient. For various reasons, the Endicott
people didn't want to make SQL/DS release dependent on getting
enhancements into VM370 ... and so that had to be dropped.

-- 
virtualization experience starting Jan1968, online at home since Mar1970

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

Re: Compile error

[Anne & Lynn Wheeler]

other trivia from ibm jargon:

MVM - n. Multiple Virtual Memory. The original name for MVS (q.v.),
which fell foul of the fashion of changing memory to storage.

MVS - n. Multiple Virtual Storage, an alternate name for OS/VS2
(Release 2), and hence a direct descendent of OS. OS/VS2 (Release 1)
was in fact the last release of OS MVT, to which paging had been
added; it was known by some as SVS (Single Virtual Storage). MVS is
one of the big two operating systems for System/370 computers (the
other being VM (q.v.)). n. Man Versus System.

... snip ...

as part of the "Man Versus System" theme ... it had become significantly
much easier to work out lots of computer concepts and design on
vm370/cms ... and then later port the implementation to MVS ... than
trying to start on an MVS base.

some time ago, I got a request about the history of adding virtual
memory to all 370s ... old post with exchange from IBMer involved (who
recently passed) with references of os/v2, future systems, hasp/asp,
etc
http://www.garlic.com/~lynn/2011d.html#73

other parts of the thread
http://www.garlic.com/~lynn/2011d.html#71
http://www.garlic.com/~lynn/2011d.html#72
http://www.garlic.com/~lynn/2011d.html#74


-- 
virtualization experience starting Jan1968, online at home since Mar1970

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

Re: Man Versus System

[John McKown]

On Fri, Jan 22, 2016 at 1:12 PM, Rick Troth  wrote:

> Helpful, because I am preparing yet another MF intro,
> where the acronyms seem to be what confuse non-mainframers more than
> anything else.
>
> Where do you place VSE? (since it's not one of "the big two")
>

​Descended from DOS.​
https://en.wikipedia.org/wiki/DOS/360_and_successors



>
> Lineage of TPF would also be interesting.
>

​Descended from ACP (Airline Control Program).
https://en.wikipedia.org/wiki/IBM_Airline_Control_Program​

I worked at Braniff Airways before it went under. The reservation system
ran ACP on a 2 Meg 3033. The thing would IPL in about 5 seconds. The ACP
systems people were a bit strange. They had the source and modified it. I
remember the CE complaining that the ACP attached tapes (3420s) would just
die with "no warnings at all" whereas the MVT (yes MVT on a 3033) and, a
bit later MVS and VM would show temp errors. The ACP people then told the
CE that they had removed all logging of temporary errors to speed up
processing. Not just on the tapes, but on the 3344 disks as well. IIRC, the
3344s on ACP actually used "software duplexing" for reliability.

-- 
Werner Heisenberg is driving down the autobahn. A police officer pulls
him over. The officer says, "Excuse me, sir, do you know how fast you
were going?"
"No," replies Dr. Heisenberg, "but I know where I am."

Computer Science is the only discipline in which we view adding a new wing
to a building as being maintenance -- Jim Horning

Schrodinger's backup: The condition of any backup is unknown until a
restore is attempted.

He's about as useful as a wax frying pan.

Maranatha! <><
John McKown

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

Man Versus System

[Rick Troth]

On 01/22/2016 01:40 PM, Anne & Lynn Wheeler wrote:

other trivia from ibm jargon:

MVM - n. Multiple Virtual Memory. The original name for MVS (q.v.),
which fell foul of the fashion of changing memory to storage.

MVS - n. Multiple Virtual Storage, an alternate name for OS/VS2
(Release 2), and hence a direct descendent of OS. OS/VS2 (Release 1)
was in fact the last release of OS MVT, to which paging had been
added; it was known by some as SVS (Single Virtual Storage). MVS is
one of the big two operating systems for System/370 computers (the
other being VM (q.v.)). n. Man Versus System.


Helpful, because I am preparing yet another MF intro,
where the acronyms seem to be what confuse non-mainframers more than 
anything else.


Where do you place VSE? (since it's not one of "the big two")

Lineage of TPF would also be interesting.



as part of the "Man Versus System" theme ... it had become significantly
much easier to work out lots of computer concepts and design on
vm370/cms ... and then later port the implementation to MVS ... than
trying to start on an MVS base.

some time ago, I got a request about the history of adding virtual
memory to all 370s ... old post with exchange from IBMer involved (who
recently passed) with references of os/v2, future systems, hasp/asp,
etc
http://www.garlic.com/~lynn/2011d.html#73

other parts of the thread
http://www.garlic.com/~lynn/2011d.html#71
http://www.garlic.com/~lynn/2011d.html#72
http://www.garlic.com/~lynn/2011d.html#74


Got into some discussion with Alan Altmark about VOL1 on IBMVM.
Track-and-record formatting is common with MVS, though VSE and VM (both 
CP and CMS) have less need of it. (Well ... until SSI in the VM world 
got an artificial dependency.)
Linux doesn't care, and actually works better (for a Linux/Unix person) 
when storage is just blocks.

(Track and record boundaries are discarded.)

So things like DASD labeling are software artifacts that give the 
illusion of being hardware feature, adding yet more kon-foo-zhun to the 
newcomers.


-- R; <><

--
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 source for detailed, instruction-level performance info?

[Randy Hudson]

In article <000401d140df$6f05a2a0$4d10e7e0$@att.net> Skip wrote:

> As a newbie, I got curious about the relative speed of these strategies:
>
> 1. L R15, COUNTER
> 2. A R15,=F(+1)
> 3. ST R15, COUNTER
>
> 1. L R15, COUNTER
> 2. LA R15,1(,R15) 
> 3. ST R15, COUNTER
>
> I asked my manager, who encouraged me to delve into the manual Shmuel cites.
> I decided that LA was faster because there was no storage access. The
> program ran like a banshee. It ran so fast that it was used to benchmark new
> hardware. Really!
>
> It wasn't till later that I pondered a basic flaw. As written, the program
> could not handle a counter greater than 16M because it ran in 24 bit mode.
> This was before XA. At the time I wrote it, the data base was comfortably
> within that limit, but over time, long after I had moved on, I (still)
> wonder if the application survived and if any counter ever hit the limit.
> Moral: whether or not size matters, speed is certainly not a simple metric. 

   L R15,COUNTER
   BCTR  R15,0
   STR15,COUNTER

gives a 2^31 limit, 2^32 if some care is taken when printing the totals, at
speed comparable to LA.

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

Load module management

[Brian Westerman]

Hi all,

I have a client who is looking for a way to manage moving modules from test 
into production.  They don't really have any extra money to spend, so 
preferably they would like it to be free, but low cost is also an alternative.  
They would like it to be somewhat panel driven (ISPF or COM-PLET) and it only 
needs to move the modules and keep track of who performed the move.  Anything 
else is gravy, but would probably be appreciated as well.

Does anyone have any ideas or locally written code that might fit them?

Thanks in advance,

Brian

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

Re: Compile error

[Robert A. Rosenberg]

JES3 does device allocation before the job is allowed to run. For 
tape drives it grabs the needed number of drives so you do not run 
into "Waiting for a Drive" issues. It did the same back in the 
mountable DASD days. I think it also tracks Tape Volumes so you do 
not run into "I need Volume X" but another job is current using it 
issues. IOW: It insures that once a job is allowed to start, there 
will be no delays to gain access to the devices and files it needs.


At 17:54 + on 01/22/2016, Gibney, David Allen,Jr wrote about Re: 
Compile error:


I've never worked with JES3. What does it offer in "disk and tape 
control" that DFSMS doesn't? Or, are we talking a different kind of 
control?



 -Original Message-
 From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 On Behalf Of Skip Robinson
 Sent: Friday, January 22, 2016 9:45 AM
 To: IBM-MAIN@LISTSERV.UA.EDU
 Subject: Re: Compile error

 As we saw in the recent thread on converting from JES3 to JES2, 
JES3 from the

 beginning provided function--especially in the area of data device control--
 that was never envisioned for JES2. I think that most of the recent
 convergence of function in the two products mostly involves what we think of
 as classic 'job control'. And the motivation for much of that 
convergence is to

 'elevate' function from JES to the BCP so that code has to be developed only
 once. JES3's historic foray into disk and tape control, while 
useful for shops
 that make use of it, has little to do with 'controlling jobs' in 
the original sense.


 .
 .
 .
 J.O.Skip Robinson
 Southern California Edison Company
 Electric Dragon Team Paddler
 SHARE MVS Program Co-Manager
 323-715-0595 Mobile
 jo.skip.robin...@att.net
 jo.skip.robin...@gmail.com


 > -Original Message-
 > From: IBM Mainframe Discussion List [mailto:IBM-
 m...@listserv.ua.edu]
 > On Behalf Of Staller, Allan
 > Sent: Friday, January 22, 2016 09:02 AM
 > To: IBM-MAIN@LISTSERV.UA.EDU
 > Subject: [Bulk] Re: Compile error
 >
 > 
 > Meanwhile there did emerge a 'JES3', but it was not an evolutionary
 > descendant of JES2. Both products have coexisted, albeit uneasily, for
 decades.
 > We used to imagine a JES5 or JES6 (depending on one's arithmetic
 proclivity)
 > that would somehow combine the best features of both products, but it's
 > almost certainly DOA. 
 > 
 >
 > Actually this seems to be happening. Witness the recent merging of JES3
 and
 > JES2 capabilities.  8 char job classes in JES2, JES2/JES3 using common
 SAPI.
 > SDSF (formerly JES only) obtaining JES3 capabilities.
 > Dependent Job Control language in JES2 (2.2).
 >
 > And I am sure there are others.  It looks like IBM is attempting to create
 "THE
 > JES" from the capabilities of JES2 and JES3.

 --
 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: Compile error

[Robert A. Rosenberg]

At 08:50 -0800 on 01/22/2016, Skip Robinson wrote about Re: Compile error:


There never was a plain old 'JES'.


I thought the spooling subsystem in OS/VS1 was called JES.

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

Re: Compile error

[Robert A. Rosenberg]

And then there was Star Wars (AKA: A New Hope [which was added when 
the film was rereleased as part of the release of The Empire Strikes 
Back]) which opened with a crawl saying Episode 4". That was just 
because they were emulating the old serials where each segment was a 
numbered Chapter with its own title (which often reflected the 
cliffhanger being resolved or the plot point of that chapter).



At 09:57 -0800 on 01/22/2016, Skip Robinson wrote about Re: Compile error:


It's Friday, right? After the release of Mel Brooks' History of the World
Part I, he was often asked when we could expect to see Part II. He claimed
never to have intended a Part II. Then why call it Part I? Because that
qualifier is almost never used. The first one is called Name; the next one
is Name II or Name Part 2. If you think about our biz, we do the same thing.
We name all sorts of elements and components such that the first one gets a
vanilla name; the next one--usually not contemplated in the original
design--gets various kinds of qualifications. The idea of naming the very
first one with a 'two' is fallout from modern marketing obfuscation, where
ordinary logic is irrelevant or downright inimical.

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
jo.skip.robin...@att.net
jo.skip.robin...@gmail.com



 -Original Message-
 From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 On Behalf Of Pommier, Rex
 Sent: Friday, January 22, 2016 09:05 AM
 To: IBM-MAIN@LISTSERV.UA.EDU
 Subject: [Bulk] Re: Compile error

 Probably just an old fairy tale, but I was told long ago that DB2 came

about as a

 name because IBM already had IMS so the 2 in DB2 was to distinguish it as
 being IBM's second DBMS offering.

 Rex

 -Original Message-
 From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 On Behalf Of Skip Robinson
 Sent: Friday, January 22, 2016 10:51 AM
 To: IBM-MAIN@LISTSERV.UA.EDU
 Subject: Re: Compile error

 The name 'DB2' seems to have followed the 1980s tradition of what I call

'name

 bloat', the practice of inflating a moniker in one way or another to make

a

 product look more mature or more elegant. The paragon in my mind was
 dBASE II from Ashton-Tate. There never was a plain old dBASE. The roman
 numeral was added from the get-go to make the product seem new and
 improved.
 Moreover, there was never an 'Ashton'. That name was invented because,

gosh

 darn it, it sounded good hyphenated with Tate, a real person.

 Before DB2 there was precedent for name bloat within IBM. There never was

a

 plain old 'JES'. The product emerged from the cocoon as JES2. There had

been a

 predecessor product called 'HASP', which may or may not have been an
 acronym for Houston Automatic Spooling Priority, but the name 'J-E-S' was
 born complete with suffix.

 Meanwhile there did emerge a 'JES3', but it was not an evolutionary
 descendant of JES2. Both products have coexisted, albeit uneasily, for

decades.

 We used to imagine a JES5 or JES6 (depending on one's arithmetic
 proclivity) that would somehow combine the best features of both products,
 but it's almost certainly DOA. Likewise, the prospects for a 'DB3' are as

dim as a

 distant star.


--
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: Is there a source for detailed, instruction-level performance info?

[Frank Swarbrick]

Works on mine!  :-)

> Date: Fri, 22 Jan 2016 13:33:49 -0800
> From: charl...@mcn.org
> Subject: Re: Is there a source for detailed, instruction-level performance 
> info?
> To: IBM-MAIN@LISTSERV.UA.EDU
> 
> Depending on the newness of your hardware.
> 
> Charles
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Frank Swarbrick
> Sent: Friday, January 22, 2016 1:32 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Is there a source for detailed, instruction-level performance
> info?
> 
> Or dare I suggest:
> ASI  COUNTER,1
> 
> --
> 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

SRB Mode and C functions

[Janet Graff]

We recently found that a pthread_mutex_lock() issues an SVC under the covers 
which causes our code in SRB Mode to abend with a S0F8-004.

Does anyone have a list of C functions (POSIX as well as stdlib) that are 
illegal in SRB Mode?

Thanks!
Janet

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

Re: Man Versus System

[Ed Finnell]

Not nearly as unhappy as the Ops Mgr that found out they had replied "u"  
all 1000 times.
 
 
In a message dated 1/22/2016 3:51:48 P.M. Central Standard Time,  
li...@akphs.com writes:

MVS and  TPF were quite unhappy about  it.



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

Re: Compile error

[Frank Swarbrick]

In the opening crawl for the original release of Star Wars not only did not say 
"A New Hope", it also did not say Episode IV.

See it here:
https://www.youtube.com/watch?v=UKRIUiyF0N4

Frank

> Date: Fri, 22 Jan 2016 16:52:01 -0500
> From: hal9...@panix.com
> Subject: Re: Compile error
> To: IBM-MAIN@LISTSERV.UA.EDU
> 
> And then there was Star Wars (AKA: A New Hope [which was added when 
> the film was rereleased as part of the release of The Empire Strikes 
> Back]) which opened with a crawl saying Episode 4". That was just 
> because they were emulating the old serials where each segment was a 
> numbered Chapter with its own title (which often reflected the 
> cliffhanger being resolved or the plot point of that chapter).
> 
> 
> At 09:57 -0800 on 01/22/2016, Skip Robinson wrote about Re: Compile error:
> 
> >It's Friday, right? After the release of Mel Brooks' History of the World
> >Part I, he was often asked when we could expect to see Part II. He claimed
> >never to have intended a Part II. Then why call it Part I? Because that
> >qualifier is almost never used. The first one is called Name; the next one
> >is Name II or Name Part 2. If you think about our biz, we do the same thing.
> >We name all sorts of elements and components such that the first one gets a
> >vanilla name; the next one--usually not contemplated in the original
> >design--gets various kinds of qualifications. The idea of naming the very
> >first one with a 'two' is fallout from modern marketing obfuscation, where
> >ordinary logic is irrelevant or downright inimical.
> >
> >.
> >.
> >.
> >J.O.Skip Robinson
> >Southern California Edison Company
> >Electric Dragon Team Paddler
> >SHARE MVS Program Co-Manager
> >323-715-0595 Mobile
> >jo.skip.robin...@att.net
> >jo.skip.robin...@gmail.com
> >
> >
> >>  -Original Message-
> >>  From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> >>  On Behalf Of Pommier, Rex
> >>  Sent: Friday, January 22, 2016 09:05 AM
> >>  To: IBM-MAIN@LISTSERV.UA.EDU
> >>  Subject: [Bulk] Re: Compile error
> >>
> >>  Probably just an old fairy tale, but I was told long ago that DB2 came
> >about as a
> >>  name because IBM already had IMS so the 2 in DB2 was to distinguish it as
> >>  being IBM's second DBMS offering.
> >>
> >>  Rex
> >>
> >>  -Original Message-
> >>  From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> >>  On Behalf Of Skip Robinson
> >>  Sent: Friday, January 22, 2016 10:51 AM
> >>  To: IBM-MAIN@LISTSERV.UA.EDU
> >>  Subject: Re: Compile error
> >>
> >>  The name 'DB2' seems to have followed the 1980s tradition of what I call
> >'name
> >>  bloat', the practice of inflating a moniker in one way or another to make
> >a
> >>  product look more mature or more elegant. The paragon in my mind was
> >>  dBASE II from Ashton-Tate. There never was a plain old dBASE. The roman
> >>  numeral was added from the get-go to make the product seem new and
> >>  improved.
> >>  Moreover, there was never an 'Ashton'. That name was invented because,
> >gosh
> >>  darn it, it sounded good hyphenated with Tate, a real person.
> >>
> >>  Before DB2 there was precedent for name bloat within IBM. There never was
> >a
> >>  plain old 'JES'. The product emerged from the cocoon as JES2. There had
> >been a
> >>  predecessor product called 'HASP', which may or may not have been an
> >>  acronym for Houston Automatic Spooling Priority, but the name 'J-E-S' was
> >>  born complete with suffix.
> >>
> >>  Meanwhile there did emerge a 'JES3', but it was not an evolutionary
> >>  descendant of JES2. Both products have coexisted, albeit uneasily, for
> >decades.
> >>  We used to imagine a JES5 or JES6 (depending on one's arithmetic
> >>  proclivity) that would somehow combine the best features of both products,
> >>  but it's almost certainly DOA. Likewise, the prospects for a 'DB3' are as
> >dim as a
> >>  distant star.
> >
> >--
> >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: Load module management

[Lucas Rosalen]

Hi Brian,

I have never used it, but I guess this is what SCLM does, isn't it?
I also recklessly assume it's imbedded with TSO/ISPF somehow - at least
I've *always* seen it in every client's ISPF menu.

Thanks,

---
*Lucas Rosalen*
Emails: rosalen.lu...@gmail.com / *lrosa...@pl.ibm.com
*
LinkedIn: http://br.linkedin.com/in/lrosalen
Phone: +48 792 809 198


2016-01-22 11:58 GMT+01:00 Brian Westerman :

> Hi all,
>
> I have a client who is looking for a way to manage moving modules from
> test into production.  They don't really have any extra money to spend, so
> preferably they would like it to be free, but low cost is also an
> alternative.  They would like it to be somewhat panel driven (ISPF or
> COM-PLET) and it only needs to move the modules and keep track of who
> performed the move.  Anything else is gravy, but would probably be
> appreciated as well.
>
> Does anyone have any ideas or locally written code that might fit them?
>
> Thanks in advance,
>
> Brian
>
> --
> 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: Identifying creator of SMF records

[Lizette Koehler]

Alan,

I think the better forum with be either the MICS Community on CA website or 
MXG.COM 

If you have SAS and MXG or SAS and MICS, one of them might have a cross 
reference or way to determine SMF details.

I have usually maintained a text file in SYS1.PARMLIB that contains a list of 
either SVCs or SMF records for non IBM products.

If you do not have that, then you may have to find another way.  And I am not 
sure how that can be done if you do not have the ability to search any and all 
installation libraries for vendor products to see what pops up.

Sometimes shops will use the defaults supplied by the Vendors and that will be 
documented in the vendors installation manual.  So I would start with that.



Lizette



-Original Message-
>From: "Field, Alan" 
>Sent: Jan 22, 2016 2:30 PM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Identifying creator of SMF records
>
>Is there a way to identify what is creating user written SMF records?
>
>We have 210s, 230s and 254s that we can't identify the source.
>
>We've dumped the records and looked at them. Some give hints (e.g. the 230s 
>look like perhaps CA OpsMVS, the 254s perhaps something related to SAF).
>
>TIA
>
>Alan

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

Re: Identifying creator of SMF records

[Charles Mills]

> documented in the vendors installation manual.  So I would start with that

True enough, but hard to work backwards. Given "ACF2" it is fairly easy to come 
up with "230." Given "230" it is tough to come up with "ACF2" (other than from 
Cheryl's or your own list.)

Lizette makes a good point about *defaults." Almost every vendor product that 
writes a "user" SMF record gives customers the ability to customize the number 
-- so as to be able to obviate collisions. So while 230 is probably ACF2, it 
could in fact be nearly any product that writes a user SMF record, and your 
ACF2 could be writing any user SMF record number. (But that direction is easy 
-- the number will be in a documented ACF2 configuration member.)

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Friday, January 22, 2016 4:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Identifying creator of SMF records

Alan,

I think the better forum with be either the MICS Community on CA website or 
MXG.COM 

If you have SAS and MXG or SAS and MICS, one of them might have a cross 
reference or way to determine SMF details.

I have usually maintained a text file in SYS1.PARMLIB that contains a list of 
either SVCs or SMF records for non IBM products.

If you do not have that, then you may have to find another way.  And I am not 
sure how that can be done if you do not have the ability to search any and all 
installation libraries for vendor products to see what pops up.

Sometimes shops will use the defaults supplied by the Vendors and that will be 
documented in the vendors installation manual.  So I would start with that.

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

Re: SRB Mode and C functions

[Sam Siegel]

Look in the XL C/C++ run time library reference in appendix B Function
Support Table.  It provides a comprehensive list of functions which can be
used under an SRB.

Sam

On Fri, Jan 22, 2016 at 2:43 PM, Janet Graff <
004dc9e91b6d-dmarc-requ...@listserv.ua.edu> wrote:

> We recently found that a pthread_mutex_lock() issues an SVC under the
> covers which causes our code in SRB Mode to abend with a S0F8-004.
>
> Does anyone have a list of C functions (POSIX as well as stdlib) that are
> illegal in SRB Mode?
>
> Thanks!
> Janet
>
> --
> 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: SRB Mode and C functions

[Tony Harminc]

On 22 January 2016 at 17:43, Janet Graff
<004dc9e91b6d-dmarc-requ...@listserv.ua.edu> wrote:
> We recently found that a pthread_mutex_lock() issues an SVC under the covers 
> which causes our
> code in SRB Mode to abend with a S0F8-004.
>
> Does anyone have a list of C functions (POSIX as well as stdlib) that are 
> illegal in SRB Mode?

I'm not sure that running with the standard C library and LE is
supported at all in SRB mode. You may  need either Metal C or the
older System Programming C.

Well... I see the LE Vendor Interfaces book does have some discussion
of SRB mode and its many difficulties, so it can't be impossible. But
this is in the context of preinitialization via CEEPIPI or the CWI
interfaces. As that book says, "Restrictions exist when running a
routine in SRB mode. For instance, an SRB routine cannot issue any
SVCs (except for ABEND). This restriction causes difficulties when
attempting to use Language Environment in SRB mode; since the default
operating system services that Language Environment uses make calls to
SVCs. "

I'm a little surprised that you got your code running in SRB mode in
the first place. How did you manage that?

Anyway - others have more experience and will surely comment.

Tony H.

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

Re: Identifying creator of SMF records

[Ed Gould]

On Jan 22, 2016, at 8:22 PM, Barry Merrill wrote:

---SNIP--
you can often identify the creator and find the SYSPROG who chose  
that SMF

record type to confirm!


Dr Merrill:
Yes this is pretty simple, in the old days. The turnover rate of  
sysprogs is fairly high and face it not all of us document things  
like this well.


I vaguely remember (years and years ago) that a vendor and Syncsort  
had the same record types and it took quite a while to figure out  
which record belonged to which vendor.


During the 3-4 months it was a PITA and arguing among the sysprogs.  
At the time we were a large(?) shop (15 sysprogs) and not all of us  
saw eye to eye on things.


I think maybe SHARE should ask the vendors to standardize something  
like vendor and version of the product (along with the standard IBM  
fields) at the beginning.


Ed

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

Re: Identifying creator of SMF records

[Field, Alan]

Thanks Lizette. We use IEASVC00 to keep track of SVCS but there is no defined 
member to register SMF numbers. 

We have a member describing the ones in use and our keeper of SMF has just 
noticed three record types are unidentified hence our interest.

Barry Merrill has offered assistance in identifying the mystery records.

Unfortunately we are starting at the back end. We have the records, browsing 
them hasn't helped particularly and there are potentially many vendors docs to 
have to wade through looking for default numbers.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Friday, January 22, 2016 6:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Identifying creator of SMF records

Alan,

I think the better forum with be either the MICS Community on CA website or 
MXG.COM 

If you have SAS and MXG or SAS and MICS, one of them might have a cross 
reference or way to determine SMF details.

I have usually maintained a text file in SYS1.PARMLIB that contains a list of 
either SVCs or SMF records for non IBM products.

If you do not have that, then you may have to find another way.  And I am not 
sure how that can be done if you do not have the ability to search any and all 
installation libraries for vendor products to see what pops up.

Sometimes shops will use the defaults supplied by the Vendors and that will be 
documented in the vendors installation manual.  So I would start with that.



Lizette



-Original Message-
>From: "Field, Alan" 
>Sent: Jan 22, 2016 2:30 PM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Identifying creator of SMF records
>
>Is there a way to identify what is creating user written SMF records?
>
>We have 210s, 230s and 254s that we can't identify the source.
>
>We've dumped the records and looked at them. Some give hints (e.g. the 230s 
>look like perhaps CA OpsMVS, the 254s perhaps something related to SAF).
>
>TIA
>
>Alan

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


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


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

Re: System check stopped state - what is it?

[Jousma, David]

I didn't look the code up, but I'm assuming you did a POR with an updated IOCDS?

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

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of R.S.
Sent: Friday, January 22, 2016 10:02 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: System check stopped state - what is it?

Unfortunately no
HW message: A logically partitioned mode event occurred. Select Details for 
information.
Details: Logical partition LPAR01 is in the system check stopped state. 
Reason code = 0C.

Note, it's not wait state, just "system check stopped state".
I tried to use google, searched PoP and some other sources with no effect.

I believe it is documented, but where???

Regards
--
Radoslaw Skorupka
Lodz, Poland






W dniu 2016-01-22 o 15:51, Vernooij, CP (ITOPT1) - KLM pisze:
> No messges id?
> POP has some information about machine-checks and check-stop conditions, but 
> I couldn't find a 0C quickly.
>
> Kees.
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of R.S.
> Sent: 22 January, 2016 15:35
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: System check stopped state - what is it?
>
> I tried to perform LOAD on some LPAR.
> I've got the following message:
>
> Logical partition LPAR01 is in the system check stopped state. Reason
> code = 0C.
>
> Where to find the meaning of the code?
>
>
> It is z13 machine.
>




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

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

mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
www.mBank.pl, e-mail: kont...@mbank.pl
Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru 
Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. 
Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości 
wpłacony) wynosi 168.955.696 złotych.


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

This e-mail transmission contains information that is confidential and may be 
privileged.   It is intended only for the addressee(s) named above. If you 
receive this e-mail in error, please do not read, copy or disseminate it in any 
manner. If you are not the intended recipient, any disclosure, copying, 
distribution or use of the contents of this information is prohibited. Please 
reply to the message immediately by informing the sender that the message was 
misdirected. After replying, please erase it from your computer system. Your 
assistance in correcting this error is appreciated.

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

Re: System check stopped state - what is it?

[R.S.]

W dniu 2016-01-22 o 16:38, Jousma, David pisze:

I didn't look the code up, but I'm assuming you did a POR with an updated IOCDS?

No, the CPC has been POR-ed many days ago, other LPARs work OK.
It was dufing operating system LOAD (first action of IPL)

Kees,
I searched PoP for 0C and read all the occurences (not so many) with no 
effect. I could miss something or just not understand, but I haven't 
found anything applicable. I would like to "consult z13 manual", but 
...what manual? I tried to browse HMC and SE manuals, even Service Guide 
or Installation Manual for Physical Planning, or Installation Manual.

I have really no idea where to search.

John,
You found (guessed?) the reason: it was z/OS IPL volume used on "Linux" 
type LPAR. Actually there were no Linux (z/VM instead) involed, but 
actually the problem is lack of documentation.
BTW: I had some other, untypical for me, problems during LOAD, but I 
solved it by intuition.



Gentlemen, thank you all for your help, I appreciate it!

Regards
--
Radoslaw Skorupka
Lodz, Poland






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

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

mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
www.mBank.pl, e-mail: kont...@mbank.pl
Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru 
Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. 
Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości 
wpłacony) wynosi 168.955.696 złotych.


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

Re: Compile error

[Staller, Allan]

Meanwhile there did emerge a 'JES3', but it was not an evolutionary descendant 
of JES2. Both products have coexisted, albeit uneasily, for decades. We used to 
imagine a JES5 or JES6 (depending on one's arithmetic proclivity) that would 
somehow combine the best features of both products, but it's almost certainly 
DOA. 


Actually this seems to be happening. Witness the recent merging of JES3 and 
JES2 capabilities.  8 char job classes in JES2, JES2/JES3 using common SAPI. 
SDSF (formerly JES only) obtaining JES3 capabilities.
Dependent Job Control language in JES2 (2.2).

And I am sure there are others.  It looks like IBM is attempting to create "THE 
JES" from the capabilities of JES2 and JES3.

Just my $0.02 USD worth...

This email – including attachments – may contain confidential information. If 
you are not the intended recipient, do not copy, distribute or act on it. 
Instead, notify the sender immediately and delete the message.

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

Re: Compile error

[Pommier, Rex]

Probably just an old fairy tale, but I was told long ago that DB2 came about as 
a name because IBM already had IMS so the 2 in DB2 was to distinguish it as 
being IBM's second DBMS offering.

Rex

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Skip Robinson
Sent: Friday, January 22, 2016 10:51 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Compile error

The name 'DB2' seems to have followed the 1980s tradition of what I call
'name bloat', the practice of inflating a moniker in one way or another to
make a product look more mature or more elegant. The paragon in my mind was
dBASE II from Ashton-Tate. There never was a plain old dBASE. The roman
numeral was added from the get-go to make the product seem new and improved.
Moreover, there was never an 'Ashton'. That name was invented because, gosh
darn it, it sounded good hyphenated with Tate, a real person. 

Before DB2 there was precedent for name bloat within IBM. There never was a
plain old 'JES'. The product emerged from the cocoon as JES2. There had been
a predecessor product called 'HASP', which may or may not have been an
acronym for Houston Automatic Spooling Priority, but the name 'J-E-S' was
born complete with suffix. 

Meanwhile there did emerge a 'JES3', but it was not an evolutionary
descendant of JES2. Both products have coexisted, albeit uneasily, for
decades. We used to imagine a JES5 or JES6 (depending on one's arithmetic
proclivity) that would somehow combine the best features of both products,
but it's almost certainly DOA. Likewise, the prospects for a 'DB3' are as
dim as a distant star.

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
jo.skip.robin...@att.net
jo.skip.robin...@gmail.com

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

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

Re: Adrdssu restore error ADR380E RC60

[Staller, Allan]

RTFM. 

60
The requested data set is a PDSE, HFS or an extended sequential data set, 
but there is a pre-allocated target data set that is a different type or has 
different attributes.


 file, I am receiving this error message.

ADR380E (001)-FRLBO(06), DATA SET SYS1.PKZIP.R80.XXX NOT PROCESSED, 60

ADR380E (001)-FRLBO(06), DATA SET SYS1.PKZIP.R80.XXX NOT PROCESSED, 60

ADR380E (001)-FRLBO(06), DATA SET SYS1.PKZIP.R80. NOT PROCESSED, 60

ADR380E (001)-FRLBO(06), DATA SET SYS1.PKZIP.R80.XXX NOT PROCESSED, 60

ADR380E (001)-FRLBO(06), DATA SET SYS1.PKZIP.R80. NOT PROCESSED, 60


I have used REPLACEU but seems not to be not working. I the target user catalog 
do not have the above entries but still get the error message.


This email � including attachments � may contain confidential information. If 
you are not the intended recipient, do not copy, distribute or act on it. 
Instead, notify the sender immediately and delete the message.

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

Re: Load module management

[Staller, Allan]

SCLM was my first take

Panvalet and Librarian also perform SCLM like functions...

After that the  go way up


I have a client who is looking for a way to manage moving modules from test 
into production.  They don't really have any extra money to spend, so 
preferably they would like it to be free, but low cost is also an alternative.  
They would like it to be somewhat panel driven (ISPF or COM-PLET) and it only 
needs to move the modules and keep track of who performed the move.  Anything 
else is gravy, but would probably be appreciated as well.

Does anyone have any ideas or locally written code that might fit them?


This email � including attachments � may contain confidential information. If 
you are not the intended recipient, do not copy, distribute or act on it. 
Instead, notify the sender immediately and delete the message.

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

Re: Compile error

[Skip Robinson]

The name 'DB2' seems to have followed the 1980s tradition of what I call
'name bloat', the practice of inflating a moniker in one way or another to
make a product look more mature or more elegant. The paragon in my mind was
dBASE II from Ashton-Tate. There never was a plain old dBASE. The roman
numeral was added from the get-go to make the product seem new and improved.
Moreover, there was never an 'Ashton'. That name was invented because, gosh
darn it, it sounded good hyphenated with Tate, a real person. 

Before DB2 there was precedent for name bloat within IBM. There never was a
plain old 'JES'. The product emerged from the cocoon as JES2. There had been
a predecessor product called 'HASP', which may or may not have been an
acronym for Houston Automatic Spooling Priority, but the name 'J-E-S' was
born complete with suffix. 

Meanwhile there did emerge a 'JES3', but it was not an evolutionary
descendant of JES2. Both products have coexisted, albeit uneasily, for
decades. We used to imagine a JES5 or JES6 (depending on one's arithmetic
proclivity) that would somehow combine the best features of both products,
but it's almost certainly DOA. Likewise, the prospects for a 'DB3' are as
dim as a distant star.

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
jo.skip.robin...@att.net
jo.skip.robin...@gmail.com

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Anne & Lynn Wheeler
> Sent: Thursday, January 21, 2016 10:53 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [Bulk] Re: Compile error
> 
> thomas.sa...@fiserv.com (Savor, Thomas  , Alpharetta) writes:
> > Management System or DBMS in 1983 when IBM >released DB2 on its MVS
> > mainframe platform." -- Wikipedia, citing an IBM manual as authority.
> >
> > All these years, I've have only known of DB2.  The name seems to have
stuck.
> >
> > Was there ever a DB1 ??
> > Will there ever be a DB3 ??
> 
> The original sql/relational implementation was at SJR (bldg. 28 on main
plant
> site, using modified vm/370 on 370/145), System/R. History/Reunion:
> http://www.mcjones.org/System_R/
> wiki
> https://en.wikipedia.org/wiki/IBM_System_R
> and another history
> http://www.theregister.co.uk/2013/11/20/ibm_system_r_making_relational_
> really_real/
> and
> http://www.cs.ubc.ca/~rap/teaching/504/2010/readings/history-of-system-
> r.pdf
> 
> The official new DBMS project was EAGLE  with the corporation focused
on
> EAGLE it was possible to get System/R out the door as SQL/DS (under the
> radar).
> 
> When EAGLE imploded, there was a request about how fast would it take to
> port System/R to MVS ... eventually released as DB2 (originally for
analytical &
> decision support *only*).
> 
> past posts mentioning System/R
> http://www.garlic.com/~lynn/submain.html#systemr
> also referenced here
> http://www.mcjones.org/System_R/citations.html
> 
> The Birth of SQL
> http://www.mcjones.org/System_R/SQL_Reunion_95/sqlr95-The.html
> 
> Some discussion of EAGLE and then DB2
> http://www.mcjones.org/System_R/SQL_Reunion_95/sqlr95-DB2.html
> 
> I periodically reference this post about Jan1992 meeting in Ellison's
conference
> room
> http://www.garlic.com/~lynn/95.html#13
> 
> one of the people in the meeting would tell how he was responsible for the
> majority of the tech transfer into the Santa Teresa Lab (now silicon
valley lab)
> for DB2.
> 
> Jim Gray departs for Tandem palming off some number of things on me ...
old
> email ref:
> http://www.garlic.com/~lynn/2007.html#email801016
> 
> Eventually IBM Toronto starts RDBMS for IBM/PC ... implemented in C ..
> which is made available on other platforms and is also called DB2 ... even
> though it is totally different code base from the mainframe
implementation.
> 
> SQL/DS is also eventually renamed DB2
> https://en.wikipedia.org/wiki/IBM_SQL/DS
> 
> --
> virtualization experience starting Jan1968, online at home since Mar1970

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

Re: Compile error

[Richard Pinion]

JES2 was a half ASP project, just a little play on words :) 



--- jo.skip.robin...@att.net wrote:

From: Skip Robinson 
To:   IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Compile error
Date: Fri, 22 Jan 2016 08:50:43 -0800

The name 'DB2' seems to have followed the 1980s tradition of what I call
'name bloat', the practice of inflating a moniker in one way or another to
make a product look more mature or more elegant. The paragon in my mind was
dBASE II from Ashton-Tate. There never was a plain old dBASE. The roman
numeral was added from the get-go to make the product seem new and improved.
Moreover, there was never an 'Ashton'. That name was invented because, gosh
darn it, it sounded good hyphenated with Tate, a real person. 

Before DB2 there was precedent for name bloat within IBM. There never was a
plain old 'JES'. The product emerged from the cocoon as JES2. There had been
a predecessor product called 'HASP', which may or may not have been an
acronym for Houston Automatic Spooling Priority, but the name 'J-E-S' was
born complete with suffix. 

Meanwhile there did emerge a 'JES3', but it was not an evolutionary
descendant of JES2. Both products have coexisted, albeit uneasily, for
decades. We used to imagine a JES5 or JES6 (depending on one's arithmetic
proclivity) that would somehow combine the best features of both products,
but it's almost certainly DOA. Likewise, the prospects for a 'DB3' are as
dim as a distant star.

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
jo.skip.robin...@att.net
jo.skip.robin...@gmail.com

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Anne & Lynn Wheeler
> Sent: Thursday, January 21, 2016 10:53 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [Bulk] Re: Compile error
> 
> thomas.sa...@fiserv.com (Savor, Thomas  , Alpharetta) writes:
> > Management System or DBMS in 1983 when IBM >released DB2 on its MVS
> > mainframe platform." -- Wikipedia, citing an IBM manual as authority.
> >
> > All these years, I've have only known of DB2.  The name seems to have
stuck.
> >
> > Was there ever a DB1 ??
> > Will there ever be a DB3 ??
> 
> The original sql/relational implementation was at SJR (bldg. 28 on main
plant
> site, using modified vm/370 on 370/145), System/R. History/Reunion:
> http://www.mcjones.org/System_R/
> wiki
> https://en.wikipedia.org/wiki/IBM_System_R
> and another history
> http://www.theregister.co.uk/2013/11/20/ibm_system_r_making_relational_
> really_real/
> and
> http://www.cs.ubc.ca/~rap/teaching/504/2010/readings/history-of-system-
> r.pdf
> 
> The official new DBMS project was EAGLE  with the corporation focused
on
> EAGLE it was possible to get System/R out the door as SQL/DS (under the
> radar).
> 
> When EAGLE imploded, there was a request about how fast would it take to
> port System/R to MVS ... eventually released as DB2 (originally for
analytical &
> decision support *only*).
> 
> past posts mentioning System/R
> http://www.garlic.com/~lynn/submain.html#systemr
> also referenced here
> http://www.mcjones.org/System_R/citations.html
> 
> The Birth of SQL
> http://www.mcjones.org/System_R/SQL_Reunion_95/sqlr95-The.html
> 
> Some discussion of EAGLE and then DB2
> http://www.mcjones.org/System_R/SQL_Reunion_95/sqlr95-DB2.html
> 
> I periodically reference this post about Jan1992 meeting in Ellison's
conference
> room
> http://www.garlic.com/~lynn/95.html#13
> 
> one of the people in the meeting would tell how he was responsible for the
> majority of the tech transfer into the Santa Teresa Lab (now silicon
valley lab)
> for DB2.
> 
> Jim Gray departs for Tandem palming off some number of things on me ...
old
> email ref:
> http://www.garlic.com/~lynn/2007.html#email801016
> 
> Eventually IBM Toronto starts RDBMS for IBM/PC ... implemented in C ..
> which is made available on other platforms and is also called DB2 ... even
> though it is totally different code base from the mainframe
implementation.
> 
> SQL/DS is also eventually renamed DB2
> https://en.wikipedia.org/wiki/IBM_SQL/DS
> 
> --
> virtualization experience starting Jan1968, online at home since Mar1970

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




_
Netscape.  Just the Net You Need.

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

Re: System check stopped state - what is it?

[Jousma, David]

I found information about check stop in the z/architecture POP CH11 PG 11-10

System Check Stop
In a multiprocessing configuration, some errors, malfunctions,
and damage conditions are of such severity
that the condition causes all CPUs in the
configuration to enter the check-stop state. This condition
is called a system check stop. The state of the
channel subsystem and I/O activity is unpredictable.

I could not find a table that described reason code 0C.
_
Dave Jousma
Assistant Vice President, Mainframe Engineering
david.jou...@53.com
1830 East Paris, Grand Rapids, MI  49546 MD RSCB2H
p 616.653.8429
f 616.653.2717


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jousma, David
Sent: Friday, January 22, 2016 10:39 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: System check stopped state - what is it?

I didn't look the code up, but I'm assuming you did a POR with an updated IOCDS?

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

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of R.S.
Sent: Friday, January 22, 2016 10:02 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: System check stopped state - what is it?

Unfortunately no
HW message: A logically partitioned mode event occurred. Select Details for 
information.
Details: Logical partition LPAR01 is in the system check stopped state. 
Reason code = 0C.

Note, it's not wait state, just "system check stopped state".
I tried to use google, searched PoP and some other sources with no effect.

I believe it is documented, but where???

Regards
--
Radoslaw Skorupka
Lodz, Poland






W dniu 2016-01-22 o 15:51, Vernooij, CP (ITOPT1) - KLM pisze:
> No messges id?
> POP has some information about machine-checks and check-stop conditions, but 
> I couldn't find a 0C quickly.
>
> Kees.
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of R.S.
> Sent: 22 January, 2016 15:35
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: System check stopped state - what is it?
>
> I tried to perform LOAD on some LPAR.
> I've got the following message:
>
> Logical partition LPAR01 is in the system check stopped state. Reason 
> code = 0C.
>
> Where to find the meaning of the code?
>
>
> It is z13 machine.
>




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

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

mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
www.mBank.pl, e-mail: kont...@mbank.pl Sąd Rejonowy dla m. st. Warszawy XII 
Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców 
KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2016 r. kapitał 
zakładowy mBanku S.A. (w całości wpłacony) wynosi 168.955.696 złotych.


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

This e-mail transmission contains information that is confidential and may be 
privileged.   It is intended only for the addressee(s) named above. If you 
receive this e-mail in error, please do not read, copy or disseminate it in any 
manner. If you are not the intended recipient, any disclosure, copying, 
distribution or use of the contents of this information is prohibited. Please 
reply to the message immediately by informing 

System check stopped state - what is it?

[R.S.]

I tried to perform LOAD on some LPAR.
I've got the following message:

Logical partition LPAR01 is in the system check stopped state. Reason 
code = 0C.


Where to find the meaning of the code?


It is z13 machine.

--
Radoslaw Skorupka
Lodz, Poland






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

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

mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
www.mBank.pl, e-mail: kont...@mbank.pl
Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru 
Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. 
Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości 
wpłacony) wynosi 168.955.696 złotych.


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

Re: System check stopped state - what is it?

[John McKown]

What OS? Any chance it is z/OS and you have an IFL defined in the LPAR?
Pure guess on my part.

2016-01-22 8:35 GMT-06:00 R.S. :

> I tried to perform LOAD on some LPAR.
> I've got the following message:
>
> Logical partition LPAR01 is in the system check stopped state. Reason code
> = 0C.
>
> Where to find the meaning of the code?
>
>
> It is z13 machine.
>
> --
> Radoslaw Skorupka
> Lodz, Poland
>
>
>
>
>
>
> ---
> Treść tej wiadomości może zawierać informacje prawnie chronione Banku
> przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być
> jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś
> adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej
> przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie,
> rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie
> zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo,
> prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale
> usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub
> zapisane na dysku.
>
> This e-mail may contain legally privileged information of the Bank and is
> intended solely for business use of the addressee. This e-mail may only be
> received by the addressee and may not be disclosed to any third parties. If
> you are not the intended addressee of this e-mail or the employee
> authorized to forward it to the addressee, be advised that any
> dissemination, copying, distribution or any other similar activity is
> legally prohibited and may be punishable. If you received this e-mail by
> mistake please advise the sender immediately by using the reply facility in
> your e-mail software and delete permanently this e-mail including any
> copies of it either printed or saved to hard drive.
>
> mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,
> www.mBank.pl, e-mail: kont...@mbank.pl
> Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego
> Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP:
> 526-021-50-88. Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku
> S.A. (w całości wpłacony) wynosi 168.955.696 złotych.
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>



-- 
Werner Heisenberg is driving down the autobahn. A police officer pulls
him over. The officer says, "Excuse me, sir, do you know how fast you
were going?"
"No," replies Dr. Heisenberg, "but I know where I am."

Computer Science is the only discipline in which we view adding a new wing
to a building as being maintenance -- Jim Horning

Schrodinger's backup: The condition of any backup is unknown until a
restore is attempted.

He's about as useful as a wax frying pan.

Maranatha! <><
John McKown

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

Re: System check stopped state - what is it?

[Vernooij, CP (ITOPT1) - KLM]

No messges id?
POP has some information about machine-checks and check-stop conditions, but I 
couldn't find a 0C quickly. 

Kees.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of R.S.
Sent: 22 January, 2016 15:35
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: System check stopped state - what is it?

I tried to perform LOAD on some LPAR.
I've got the following message:

Logical partition LPAR01 is in the system check stopped state. Reason 
code = 0C.

Where to find the meaning of the code?


It is z13 machine.

-- 
Radoslaw Skorupka
Lodz, Poland






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

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

mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
www.mBank.pl, e-mail: kont...@mbank.pl
Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru 
Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. 
Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości 
wpłacony) wynosi 168.955.696 złotych.


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

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

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



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

Re: System check stopped state - what is it?

[R.S.]

Unfortunately no
HW message: A logically partitioned mode event occurred. Select Details 
for information.
Details: Logical partition LPAR01 is in the system check stopped state. 
Reason code = 0C.


Note, it's not wait state, just "system check stopped state".
I tried to use google, searched PoP and some other sources with no effect.

I believe it is documented, but where???

Regards
--
Radoslaw Skorupka
Lodz, Poland






W dniu 2016-01-22 o 15:51, Vernooij, CP (ITOPT1) - KLM pisze:

No messges id?
POP has some information about machine-checks and check-stop conditions, but I 
couldn't find a 0C quickly.

Kees.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of R.S.
Sent: 22 January, 2016 15:35
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: System check stopped state - what is it?

I tried to perform LOAD on some LPAR.
I've got the following message:

Logical partition LPAR01 is in the system check stopped state. Reason
code = 0C.

Where to find the meaning of the code?


It is z13 machine.






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

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

mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
www.mBank.pl, e-mail: kont...@mbank.pl
Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru 
Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. 
Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości 
wpłacony) wynosi 168.955.696 złotych.


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

Re: System check stopped state - what is it?

[Donald J.]

Is you IODF volume address correct?

Maybe try following these instructions to display the
IPL Vector Table control block which is mapped by
SYS1.MODGEN(IHAIVT)

Using the hardware Alter/Display facility, read the real address in central 
storage at X'14'. 
This address points to the IPL diagnostic area.
Add X'28' to the address in X'14', and also read this as a real address in 
central storage. 
The result is the 31-bit virtual address of the IPL vector table (IVT).

-- 
  Donald J.
  dona...@4email.net

On Fri, Jan 22, 2016, at 06:35 AM, R.S. wrote:
> I tried to perform LOAD on some LPAR.
> I've got the following message:
> 
> Logical partition LPAR01 is in the system check stopped state. Reason 
> code = 0C.
> 
> Where to find the meaning of the code?
> 
> 
> It is z13 machine.
> 
> -- 
> Radoslaw Skorupka
> Lodz, Poland
> 
> 
> 
> 
> 
> 
> ---
> Treść tej wiadomości może zawierać informacje prawnie chronione Banku 
> przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być 
> jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś 
> adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej 
> przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, 
> rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie 
> zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, 
> prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale 
> usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub 
> zapisane na dysku.
> 
> This e-mail may contain legally privileged information of the Bank and is 
> intended solely for business use of the addressee. This e-mail may only be 
> received by the addressee and may not be disclosed to any third parties. If 
> you are not the intended addressee of this e-mail or the employee authorized 
> to forward it to the addressee, be advised that any dissemination, copying, 
> distribution or any other similar activity is legally prohibited and may be 
> punishable. If you received this e-mail by mistake please advise the sender 
> immediately by using the reply facility in your e-mail software and delete 
> permanently this e-mail including any copies of it either printed or saved to 
> hard drive.
> 
> mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
> www.mBank.pl, e-mail: kont...@mbank.pl
> Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru 
> Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. 
> Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości 
> wpłacony) wynosi 168.955.696 złotych.
> 
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

-- 
http://www.fastmail.com - Or how I learned to stop worrying and
  love email again

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

Re: Compile error

[Skip Robinson]

As we saw in the recent thread on converting from JES3 to JES2, JES3 from
the beginning provided function--especially in the area of data device
control--that was never envisioned for JES2. I think that most of the recent
convergence of function in the two products mostly involves what we think of
as classic 'job control'. And the motivation for much of that convergence is
to 'elevate' function from JES to the BCP so that code has to be developed
only once. JES3's historic foray into disk and tape control, while useful
for shops that make use of it, has little to do with 'controlling jobs' in
the original sense. 

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
jo.skip.robin...@att.net
jo.skip.robin...@gmail.com


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Staller, Allan
> Sent: Friday, January 22, 2016 09:02 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [Bulk] Re: Compile error
> 
> 
> Meanwhile there did emerge a 'JES3', but it was not an evolutionary
> descendant of JES2. Both products have coexisted, albeit uneasily, for
decades.
> We used to imagine a JES5 or JES6 (depending on one's arithmetic
proclivity)
> that would somehow combine the best features of both products, but it's
> almost certainly DOA. 
> 
> 
> Actually this seems to be happening. Witness the recent merging of JES3
and
> JES2 capabilities.  8 char job classes in JES2, JES2/JES3 using common
SAPI.
> SDSF (formerly JES only) obtaining JES3 capabilities.
> Dependent Job Control language in JES2 (2.2).
> 
> And I am sure there are others.  It looks like IBM is attempting to create
"THE
> JES" from the capabilities of JES2 and JES3.

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

Re: Compile error

[McCabe, Ron]

So where does DL1 fit in?

Ron McCabe
Mutual of Enumclaw

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Pommier, Rex
Sent: Friday, January 22, 2016 9:05 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Compile error

Probably just an old fairy tale, but I was told long ago that DB2 came about as 
a name because IBM already had IMS so the 2 in DB2 was to distinguish it as 
being IBM's second DBMS offering.

Rex

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Skip Robinson
Sent: Friday, January 22, 2016 10:51 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Compile error

The name 'DB2' seems to have followed the 1980s tradition of what I call 'name 
bloat', the practice of inflating a moniker in one way or another to make a 
product look more mature or more elegant. The paragon in my mind was dBASE II 
from Ashton-Tate. There never was a plain old dBASE. The roman numeral was 
added from the get-go to make the product seem new and improved.
Moreover, there was never an 'Ashton'. That name was invented because, gosh 
darn it, it sounded good hyphenated with Tate, a real person.

Before DB2 there was precedent for name bloat within IBM. There never was a 
plain old 'JES'. The product emerged from the cocoon as JES2. There had been a 
predecessor product called 'HASP', which may or may not have been an acronym 
for Houston Automatic Spooling Priority, but the name 'J-E-S' was born complete 
with suffix.

Meanwhile there did emerge a 'JES3', but it was not an evolutionary descendant 
of JES2. Both products have coexisted, albeit uneasily, for decades. We used to 
imagine a JES5 or JES6 (depending on one's arithmetic
proclivity) that would somehow combine the best features of both products, but 
it's almost certainly DOA. Likewise, the prospects for a 'DB3' are as dim as a 
distant star.

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
jo.skip.robin...@att.net
jo.skip.robin...@gmail.com

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

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Confidentiality Notice: This e- mail and all attachments may contain 
CONFIDENTIAL information and are meant solely for the intended recipient. It 
may contain controlled, privileged, or proprietary information that is 
protected under applicable law and shall not be disclosed to any unauthorized 
third party. If you are not the intended recipient, you are hereby notified 
that any unauthorized review, action, disclosure, distribution, or reproduction 
of any information contained in this e- mail and any attachments is strictly 
PROHIBITED. If you received this e- mail in error, please reply to the sender 
immediately stating that this transmission was misdirected, and delete or 
destroy all electronic and paper copies of this e-mail and attachments without 
disclosing the contents. This e- mail does not grant or assign rights of 
ownership in the proprietary subject matter herein, nor shall it be construed 
as a joint venture, partnership, teaming agreement, or any other formal 
business relationship.

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

Re: Compile error

[Gibney, David Allen,Jr]

I've never worked with JES3. What does it offer in "disk and tape control" that 
DFSMS doesn't? Or, are we talking a different kind of control?

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Skip Robinson
> Sent: Friday, January 22, 2016 9:45 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Compile error
> 
> As we saw in the recent thread on converting from JES3 to JES2, JES3 from the
> beginning provided function--especially in the area of data device control--
> that was never envisioned for JES2. I think that most of the recent
> convergence of function in the two products mostly involves what we think of
> as classic 'job control'. And the motivation for much of that convergence is 
> to
> 'elevate' function from JES to the BCP so that code has to be developed only
> once. JES3's historic foray into disk and tape control, while useful for shops
> that make use of it, has little to do with 'controlling jobs' in the original 
> sense.
> 
> .
> .
> .
> J.O.Skip Robinson
> Southern California Edison Company
> Electric Dragon Team Paddler
> SHARE MVS Program Co-Manager
> 323-715-0595 Mobile
> jo.skip.robin...@att.net
> jo.skip.robin...@gmail.com
> 
> 
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-
> m...@listserv.ua.edu]
> > On Behalf Of Staller, Allan
> > Sent: Friday, January 22, 2016 09:02 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: [Bulk] Re: Compile error
> >
> > 
> > Meanwhile there did emerge a 'JES3', but it was not an evolutionary
> > descendant of JES2. Both products have coexisted, albeit uneasily, for
> decades.
> > We used to imagine a JES5 or JES6 (depending on one's arithmetic
> proclivity)
> > that would somehow combine the best features of both products, but it's
> > almost certainly DOA. 
> > 
> >
> > Actually this seems to be happening. Witness the recent merging of JES3
> and
> > JES2 capabilities.  8 char job classes in JES2, JES2/JES3 using common
> SAPI.
> > SDSF (formerly JES only) obtaining JES3 capabilities.
> > Dependent Job Control language in JES2 (2.2).
> >
> > And I am sure there are others.  It looks like IBM is attempting to create
> "THE
> > JES" from the capabilities of JES2 and JES3.
> 
> --
> 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: Compile error

[Skip Robinson]

It's Friday, right? After the release of Mel Brooks' History of the World
Part I, he was often asked when we could expect to see Part II. He claimed
never to have intended a Part II. Then why call it Part I? Because that
qualifier is almost never used. The first one is called Name; the next one
is Name II or Name Part 2. If you think about our biz, we do the same thing.
We name all sorts of elements and components such that the first one gets a
vanilla name; the next one--usually not contemplated in the original
design--gets various kinds of qualifications. The idea of naming the very
first one with a 'two' is fallout from modern marketing obfuscation, where
ordinary logic is irrelevant or downright inimical.

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
jo.skip.robin...@att.net
jo.skip.robin...@gmail.com


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Pommier, Rex
> Sent: Friday, January 22, 2016 09:05 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [Bulk] Re: Compile error
> 
> Probably just an old fairy tale, but I was told long ago that DB2 came
about as a
> name because IBM already had IMS so the 2 in DB2 was to distinguish it as
> being IBM's second DBMS offering.
> 
> Rex
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Skip Robinson
> Sent: Friday, January 22, 2016 10:51 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Compile error
> 
> The name 'DB2' seems to have followed the 1980s tradition of what I call
'name
> bloat', the practice of inflating a moniker in one way or another to make
a
> product look more mature or more elegant. The paragon in my mind was
> dBASE II from Ashton-Tate. There never was a plain old dBASE. The roman
> numeral was added from the get-go to make the product seem new and
> improved.
> Moreover, there was never an 'Ashton'. That name was invented because,
gosh
> darn it, it sounded good hyphenated with Tate, a real person.
> 
> Before DB2 there was precedent for name bloat within IBM. There never was
a
> plain old 'JES'. The product emerged from the cocoon as JES2. There had
been a
> predecessor product called 'HASP', which may or may not have been an
> acronym for Houston Automatic Spooling Priority, but the name 'J-E-S' was
> born complete with suffix.
> 
> Meanwhile there did emerge a 'JES3', but it was not an evolutionary
> descendant of JES2. Both products have coexisted, albeit uneasily, for
decades.
> We used to imagine a JES5 or JES6 (depending on one's arithmetic
> proclivity) that would somehow combine the best features of both products,
> but it's almost certainly DOA. Likewise, the prospects for a 'DB3' are as
dim as a
> distant star. 

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

Re: Identifying creator of SMF records

[Barry Merrill]

In general, you have to rely on a hex dump of a few of the user SMF records,
to look for obvious fields and contents, and ask your SYSPROGs/DBAs etc,
what products are installed.  
Sometimes there is a SUBSYSTEM ID that identifies the creator in bytes 15-18.  
You can identify lots of EBCDIC text fields by content and length, like the 
JOB, USERID, JCTJOBID, 44-byte DSNAMES, RACFGRUP names, the SMFSTAMP and 
TODSTAMP datetime fields, and along with asking what products are installed,
you can often identify the creator and find the SYSPROG who chose that SMF
record type to confirm!

But often the final identification requires visual examination 
of the record's hex dump, and to count the recognizable elements
(e.g., 2 DSNAMEs, 3 TODSTAMP, 2 SMFSTAMP, JOB JCTJOBID), and then 
examine a possible product's source member in MXG to count those
same elements in the SAS INPUT statements to find a match, and
then confirm by comparing field-by-field visually, or just
by using that MXG code member to read the record.

MXG has only 260 user SMF record members to examine.


Barry


Herbert W. “Barry” Merrill, PhD
President-Programmer
MXG Software
Merrill Consultants
10717 Cromwell Drive
Dallas, TX 75229-5112
ba...@mxg.com
Fax:  214 350 3694 – Still works, received as email
Tel:  214 351 1966 – Unreliable, please use email

www.mxg.comHomePage: FAQ answers most questions
ad...@mxg.com  License Forms, Invoice, Payment, ftp information
supp...@mxg.comTechnical Issues 
MXG-L FREE ListServer  http://www.mxg.com/mxg-l_listserver/









-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Friday, January 22, 2016 6:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Identifying creator of SMF records

Alan,

I think the better forum with be either the MICS Community on CA website or 
MXG.COM 

If you have SAS and MXG or SAS and MICS, one of them might have a cross 
reference or way to determine SMF details.

I have usually maintained a text file in SYS1.PARMLIB that contains a list of 
either SVCs or SMF records for non IBM products.

If you do not have that, then you may have to find another way.  And I am not 
sure how that can be done if you do not have the ability to search any and all 
installation libraries for vendor products to see what pops up.

Sometimes shops will use the defaults supplied by the Vendors and that will be 
documented in the vendors installation manual.  So I would start with that.



Lizette



-Original Message-
>From: "Field, Alan" 
>Sent: Jan 22, 2016 2:30 PM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Identifying creator of SMF records
>
>Is there a way to identify what is creating user written SMF records?
>
>We have 210s, 230s and 254s that we can't identify the source.
>
>We've dumped the records and looked at them. Some give hints (e.g. the 230s 
>look like perhaps CA OpsMVS, the 254s perhaps something related to SAF).
>
>TIA
>
>Alan

--
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: Compile error

[Anne & Lynn Wheeler]

hal9...@panix.com (Robert A. Rosenberg) writes:
> And then there was Star Wars (AKA: A New Hope [which was added when
> the film was rereleased as part of the release of The Empire Strikes
> Back]) which opened with a crawl saying Episode 4". That was just
> because they were emulating the old serials where each segment was a
> numbered Chapter with its own title (which often reflected the
> cliffhanger being resolved or the plot point of that chapter).

co-worker at IBM would talk about Lucas attending San Jose Astronomy
club meetings and bringing draft outlines for all 8 episodes (for
members to review) More recent interviews with Lucas says that the first
episode he chose to do, was the one most likely for getting funding.

-- 
virtualization experience starting Jan1968, online at home since Mar1970

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

Re: Identifying creator of SMF records

[Clark Morris]

On 22 Jan 2016 18:22:41 -0800, in bit.listserv.ibm-main you wrote:

>In general, you have to rely on a hex dump of a few of the user SMF records,
>to look for obvious fields and contents, and ask your SYSPROGs/DBAs etc,
>what products are installed.  
>Sometimes there is a SUBSYSTEM ID that identifies the creator in bytes 15-18.  
>You can identify lots of EBCDIC text fields by content and length, like the 
>JOB, USERID, JCTJOBID, 44-byte DSNAMES, RACFGRUP names, the SMFSTAMP and 
>TODSTAMP datetime fields, and along with asking what products are installed,
>you can often identify the creator and find the SYSPROG who chose that SMF
>record type to confirm!

Then there are shop specific USER SMF records such as the PROC usage
records written in first JES3 IATUX32 then JES2 exit 6 track use by
PROC name and concatenation used that I created at Westinghouse Lamp
Divisions which became Philips Lighting.   The JES2 exit is in the
Philips mods on the CBT Tape.

Clark Morris 
>
>But often the final identification requires visual examination 
>of the record's hex dump, and to count the recognizable elements
>(e.g., 2 DSNAMEs, 3 TODSTAMP, 2 SMFSTAMP, JOB JCTJOBID), and then 
>examine a possible product's source member in MXG to count those
>same elements in the SAS INPUT statements to find a match, and
>then confirm by comparing field-by-field visually, or just
>by using that MXG code member to read the record.
>
>MXG has only 260 user SMF record members to examine.
>
>
>Barry
>
>
>Herbert W. “Barry” Merrill, PhD
>President-Programmer
>MXG Software
>Merrill Consultants
>10717 Cromwell Drive
>Dallas, TX 75229-5112
>ba...@mxg.com
>Fax:  214 350 3694 – Still works, received as email
>Tel:  214 351 1966 – Unreliable, please use email
>
>www.mxg.comHomePage: FAQ answers most questions
>ad...@mxg.com  License Forms, Invoice, Payment, ftp information
>supp...@mxg.comTechnical Issues 
>MXG-L FREE ListServer  http://www.mxg.com/mxg-l_listserver/
>
>
>
>
>
>
>
>
>
>-Original Message-
>From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
>Behalf Of Lizette Koehler
>Sent: Friday, January 22, 2016 6:13 PM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: Identifying creator of SMF records
>
>Alan,
>
>I think the better forum with be either the MICS Community on CA website or 
>MXG.COM 
>
>If you have SAS and MXG or SAS and MICS, one of them might have a cross 
>reference or way to determine SMF details.
>
>I have usually maintained a text file in SYS1.PARMLIB that contains a list of 
>either SVCs or SMF records for non IBM products.
>
>If you do not have that, then you may have to find another way.  And I am not 
>sure how that can be done if you do not have the ability to search any and all 
>installation libraries for vendor products to see what pops up.
>
>Sometimes shops will use the defaults supplied by the Vendors and that will be 
>documented in the vendors installation manual.  So I would start with that.
>
>
>
>Lizette
>
>
>
>-Original Message-
>>From: "Field, Alan" 
>>Sent: Jan 22, 2016 2:30 PM
>>To: IBM-MAIN@LISTSERV.UA.EDU
>>Subject: Identifying creator of SMF records
>>
>>Is there a way to identify what is creating user written SMF records?
>>
>>We have 210s, 230s and 254s that we can't identify the source.
>>
>>We've dumped the records and looked at them. Some give hints (e.g. the 230s 
>>look like perhaps CA OpsMVS, the 254s perhaps something related to SAF).
>>
>>TIA
>>
>>Alan
>
>--
>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: Compile error

[Larry Chenevert]

From: Robert A. Rosenberg

There never was a plain old 'JES'.


"I thought the spooling subsystem in OS/VS1 was called JES."

You are correct: JES

Did that (VS1/JES) through a lot of of the '70's.
Then VS1 under VM, then SVS, then DOS, VS1, and MVS under VM (different 
place), then finally MVS. 


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

Re: Compile error

[Larry Chenevert]

At 08:50 -0800 on 01/22/2016, Skip Robinson wrote about Re: Compile error:


There never was a plain old 'JES'.


"I thought the spooling subsystem in OS/VS1 was called JES."

You are correct:  JES  (for VS1).

Through most of the '70's did VS1, VS1 under VM/370, SVS,
then at a different place, DOS/VSE and VS1 and MVS 3.8J under VM/370, and 
finally MVS with other combinations to get to Man Versus Machine.


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

Re: Identifying creator of SMF records

[retired mainframer]

If none of the intelligent advice helps, would the timestamp in the record
narrow it down to whatever was running at that moment?  If you have several
records of one type, only the tasks running at all those times would be
candidates.  And probably none of the IBM tasks.

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Field, Alan
> Sent: Friday, January 22, 2016 1:31 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Identifying creator of SMF records
> 
> Is there a way to identify what is creating user written SMF records?
> 
> We have 210s, 230s and 254s that we can't identify the source.
> 
> We've dumped the records and looked at them. Some give hints (e.g. the
230s look like
> perhaps CA OpsMVS, the 254s perhaps something related to SAF).
> 
> TIA

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