Hi
Cross posted
When we take a SVCDUMP for an active address space . Does the dump shows if
that particular address space uses particular EXIT ? I am just trying to
understand if a dump of an address space can help me to determine if a
particular exit is being used or not .
Any pointers would
At the point in time where I shut down ZFS, I want it to interfere, that's the
whole point.
Brian
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO
HI,
ALL commands issued at a console or from a program or JCL are processed in the
command exit, whether they are JES or MVS commands or just random text typed on
the console.
When I developed our console message processing facility, I originally set it
up to run as a command exit and then
For the benefit of other members
Test CBU Activation gave me 10 days plus 2 days of grace period
Then I was able to activate another CBU without IPLing or POR
Thanks all and thanks especially to Parwez .
On Tue, 14 May, 2019, 8:29 PM Peter, wrote:
> So to activate another test CBU. Does it
On Wed, 15 May 2019 20:31:55 +, Pommier, Rex wrote:
>The point I was making was that IBM had some DASD subsystems for large(r)
>customers with integrated controllers
Oh. Sorry I misunderstood. Thanks for the clarification.
The s/360 POO (available on bitsavers), says,
"A control unit may
GPL requires that if you modify the source and redistribute the source or
derivative works (binaries) you need to make the source available publicly. If
you get the source, modify it and use the mods in an org and are not
redistributing it you do not have to make your private work public.
Yep. Just updated my Win 10 machines. So bad they issued patches for
Win XP and up, out of support for several years.
On Wed, May 15, 2019 at 12:14 PM Bill Johnson
<0047540adefe-dmarc-requ...@listserv.ua.edu> wrote:
>
> Microsoft (MSFT) is warning users about a monster computer bug. The
On Wed, 15 May 2019 21:41:20 +, Seymour J Metz wrote:
>That may be true for 2314, but it is not true for anything later. The A unit
>connects to the control unit, not to the channel.
>
I actually intended to say that the A units connected to the control unit. I
don't know why I said
That may be true for 2314, but it is not true for anything later. The A unit
connects to the control unit, not to the channel.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Alan Altmark
Ramac I and Ramac II (9394 Controllers and 9395 Drawers) comes first from
2105/Shark and has controller (3990 like) inside same frame (small foot print)
if compared with previous 3990 and 3380 or 3390 machines.
Carlos Bodra
IBM zEnterprise Certified
São Paulo – SP – Brazil
-Mensagem
Tom,
The point I was making was that IBM had some DASD subsystems for large(r)
customers with integrated controllers unlike the 3990/3390 before the Shark. I
never had physical 3390s in any of the shops I worked at, but had 9340, RAMAC,
and RVA; and liked all of them. Definitely shrunk the
[Default] On 14 May 2019 11:23:01 -0700, in bit.listserv.ibm-main
idfli...@gmail.com (scott Ford) wrote:
>All:
>
>I need to do some research on how job is cancelled via the Operator , Abend
>S222. I read through some of the Boston share doc of some time ago by Ed,
>Sam and Skip. Its great.
>I
Dang those pesky servers
https://www.usnews.com/news/national-news/articles/2019-05-07/baltimore-targeted-by-ransomware-attack-city-shuts-down-most-of-its-servers
In a message dated 5/15/2019 12:14:19 PM Central Standard Time,
0047540adefe-dmarc-requ...@listserv.ua.edu writes:
Microsoft
On Wed, 15 May 2019 19:53:07 +, Pommier, Rex wrote:
>where did the 9340 subsystem fit in the timeline between 3990 and 2105? or the
>RAMAC2?
https://en.wikipedia.org/wiki/History_of_IBM_magnetic_disk_drives#IBM_9340_and_9345
--
Tom Marchant
It was sheer size of the componentry that drove this design. I think the 3990
was the last stand-alone disk controller. With the arrival of 2105s, the CU
was inside the same cabinet as the drives and Logical CUs (LCUs) were born.
One big black box (literally). Adding additional cabinets
On Wed, 15 May 2019 14:59:00 +0200, R.S. wrote:
>In the old days there was a Storage Control Unit, i.e. 3830 and disk
>controller within disk cabinet, i.e. 3350-A2
>
>So, we have CPC-cable1-3830-cable2-3350A2controller-internal_cable3-disk.
>
>I'm trying to understand separation of duties
On Tue, 14 May 2019 16:19:52 +, Jesse 1 Robinson wrote:
>... It has long been customary in the MVS world for each user to logon to TSO
>with a concatenation of CLIST/EXEC libraries, some supplied by infrastructure,
>some by the local 'department', and some by the individual user.
>
???
Microsoft (MSFT) is warning users about a monster computer bug. The company
says it has fixed the flaw but says it's “highly likely” that it will end up
being used by malicious software. The flaw mainly affects older systems such as
Windows 7 and Windows 2003.
On Wed, May 15, 2019 at 10:14 AM Jesse 1 Robinson
wrote:
> I was banging away at a reply for JES2 Exit 5 when I realized that most
> CANCEL commands are issued to MVS, not JES. Where would a 'C my-pet-task'
> be intercepted?
>
Perhaps?
As stated, the ARCH(n) limits the assembler instructions the compiler can
generate based on hardware capabilities. You won't get z14 vector register
instructions with ARCH(11).
Your debugger may in fact have a problem We just installed the latest PTFs for
Expediter and have no ARCH(12)
Hi Jesse,
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieae400/svc34.htm#svc34__cdemvs
Regards,
David
On 2019-05-15 11:13, Jesse 1 Robinson wrote:
> I was banging away at a reply for JES2 Exit 5 when I realized that most
> CANCEL commands are issued to MVS, not
I was banging away at a reply for JES2 Exit 5 when I realized that most CANCEL
commands are issued to MVS, not JES. Where would a 'C my-pet-task' be
intercepted?
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595
The first question is how old.
In general, a channel connects to a control unit, which either connects to an
I/O device or which also serves the role of an I/O device. A complication is
that some processors had an option for an integrated adapter that served the
role of both controller and
> The first device to support "disconnect" was the 3330
No; the 3330 was a Johnny come lately. The first device such was the 2305 fixed
head disk attached to the 2835 controller.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM
The first device to support "disconnect" was the 3330 which also connected to a
3830.
Prior to that IO in both directions tied up the entire path from CPU to device
and back for the duration (2314, 2311 dasd).
The flow of a "typical" IO request:
Channel passes commands to 3830 and disconnects.
On Wed, 15 May 2019 14:59:00 +0200, R.S. wrote:
>(this is mostly historical question)
It might be helpful to you to get a copy of the System/360 Principles
of Operation, which describes this a little bit. You can find it on bitsavers.
(this is mostly historical question)
I'm trying to understand the role of old boxes in DASD connectivity.
From IODF/HCD point of view we have
CPC-channels-CU-some_cable-DEVice
Nowadays in real world we have
CPC-ficon-DASDbox
and DASDbox is both CU+DEV (emulated).
In the old days there was a
Thanks everyone,
Gadi
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Allan Staller
Sent: Wednesday, May 15, 2019 3:39 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Logrec Logstream name
In the logger policy, and IIRC, in LOGREC= in IEASYS00.
HTH,
-Original
In the logger policy, and IIRC, in LOGREC= in IEASYS00.
HTH,
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Gadi Ben-Avi
Sent: Wednesday, May 15, 2019 7:35 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Logrec Logstream name
Thanks
Where do I define the name of the
With no coupling facility, you are limited to DASD-Only logstreams.
DASD-only logstreams *CAN NOT* be shared.
It is (IMO) not worth the effort to convert to logstreams for EREP when DASD
only.
EREP, these days, is pretty much limited to software records, and thus there is
limited value to a
PARMLIB(IEASYSxx)
LOGREC parameter
On Wed, 15 May 2019 at 15:35, Gadi Ben-Avi wrote:
> Thanks
> Where do I define the name of the logstream for LOGREC?
> Gadi
>
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf
> Of Mike Shorkend
> Sent: Wednesday, May 15, 2019 3:29
Thanks
Where do I define the name of the logstream for LOGREC?
Gadi
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Mike Shorkend
Sent: Wednesday, May 15, 2019 3:29 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Logrec Logstream name
Gadi
If you do not have a coupling
Set up the Resolver function. Pretty straightforward.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Tony Thigpen
Sent: Tuesday, May 14, 2019 5:57 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: TCPIP.DATA file
Currently, all the TCPIP jobs have to specify the //SYSTCPD
Gadi
If you do not have a coupling facility, them the logstream has to be DASD-
only and can not be shared between LPARS. See here:
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieag200/cfod.htm
You will need to use a unique name for each logstream. You could use
Found my answer in the manual (which in itself hard to find on the internet),
SYSPROG access level doesn't get you there. You need ACSADMIN access rights.
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
On 15/05/2019 12:13 am, Paul Gilmartin wrote:
On Tue, 14 May 2019 13:58:20 +0800, David Crayford wrote:
If you've got a C compiler you can build "gawk" yourself. It's already
been ported to z/OS and I can see there are z/OS specific commits as
recently as a few months ago.
Hi,
We have a basic sysplex with two members.
There is no coupling facility.
1. Is it possible to use the same logrec logstream
(SYSPLEX.LOGREC.ALLRECS) for both systems.
2. If not, how do I specify different a logstream for each system?
We are using z/OS v2.3
Gadi
Got all that already, the "Customize API settings" task isn't there, hence my
thought that it's an access level problem.
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com
‐‐‐ Original
W dniu 2019-05-07 o 23:46, Bob Bridges pisze:
Yeah, about that: What ~is~ a "controled program"? I noticed that
qualification, but my background is apps development and I'm woefully
ignorant in spots.
A controlled program is the program defined to RACF in PROGRAM class.
It can be CL(PROGRAM)
Not sure about the authority levels
- On the HMC, select the CEC, recovery, single object operations (getting into
the SE)
- Select SE management, "customize API settings"
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Mark
I'm trying to define the SNMP name in the support element on our z13s processor
and can't find "Support Element Settings" task to do so. I'm logged with
SYSPROG access rights. Do I need a different access level, or is it user error?
Mark Jacobs
Sent from [ProtonMail](https://protonmail.com),
IBM indicates ZFS is handled with ending OMVS:
"In general, do not stop zFS. Stopping zFS is disruptive to applications
that are using zFS file systems. zFS stops automatically when you shut down
z/OS® UNIX. To shut down an LPAR or to re-IPL an LPAR, use the MODIFY
OMVS,SHUTDOWN operator command
One of my coworkers produced this some years ago:
PROC to place in a common proclib:
//OESIG PROC
//***
//*** This Procedure Terminates Processes in the UNIX Environment ***
43 matches
Mail list logo
