But if the event happened, is there a way to find out what it was. The
slip, I think, would only be helpful if you were anticipating the
IEA848I.
Or is the fact this could happen lead one to always have a slip set for
IEA848I in case it happens? ;-D
The original poster indicated that
In 54b8fa04026d0017e...@prv-mh.provo.novell.com, on 01/16/2015
at 09:46 AM, Mark Post mp...@suse.com said:
You'll need to be a little more verbose. What about error recovery?
Does KVM on a bare LPAR have code to recover from I/O, memory and
processor failures? Does it have code to record
Same rule at my recent site;
with new PL/1, it is even possible to make all STATIC definitions
NONASSIGNABLE
by default, so that you have to code STATIC ASGN, if you want a STATIC
variable
to be ASSIGNABLE.
Often the PL/1 knowledge is dramatically limited by the site standards
of the site
At my recent site, we wanted all programs to be naturally reentrant
for several reasons ... no matter, if PL/1, ASSEMBLER, or C.
With the old compilers, we achieved this by telling the developers that the
STATIC variables must not be changed during execution. We had some
test systems that
For IEA848I it says
The question was how to find the task that triggered the message
because it is not authorized. It is more general and not restricted
to this specific message: How to find the task related with a
message if ther is no jobid?
SLIP
But if the event happened, is there a way to find out what it was. The
slip, I think, would only be helpful if you were anticipating the IEA848I.
Or is the fact this could happen lead one to always have a slip set for
IEA848I in case it happens? ;-D
Lizette
-Original Message-
From:
On 1/17/2015 at 06:37 PM, Shmuel Metz (Seymour J.)
shmuel+ibm-m...@patriot.net wrote:
In 54b8fa04026d0017e...@prv-mh.provo.novell.com, on 01/16/2015
at 09:46 AM, Mark Post mp...@suse.com said:
You'll need to be a little more verbose. What about error recovery?
Does KVM on a bare
On 17 January 2015 at 17:02, Jim Mulder d10j...@us.ibm.com wrote:
For IEA848I it says
The question was how to find the task that triggered the message
because it is not authorized. It is more general and not restricted
to this specific message: How to find the task related with a
message
On Sat, 17 Jan 2015 17:05:15 -0700, Mark Post wrote:
So, we don't just do z/VM, KVM, or LPARs, we do them all.
Thank you Mark, nice synopsis of what's do-able.
Now, if I can just find a customer that would do likewise ... ;-)
Shane ...
Mehrshad:
No, you do not understand. I was answering Tom on why COBOL
should be made to have access to data above the bar (2GB address
range) now, not later.
That a COBOL program can't execute in the area above 2GB is a
completely different issue.
Regards,
Steve Thompson
On 01/17/2015
Hi,
We are migrating to zOS 1.13 and in COMMNDxx I have a SETCON MODE=DISTRIBUTED.
What is the difference between MODE=DISTRIBUTED and MODE=SHARED? There are two
systems in the sysplex, having the 1.13 system with DISTRIBUTED and the 1.11
system with SHARED cause any issue?
Thank you,
Dean
SLIP SET,A=SVCD,MSGID=IEA848I,ML=1,ID=M848,END
Thanks, Jim, this confirms to me there is no way to find out from the operlog,
only.
I got this request long after the IPL from our second level. I have not yet
looked if it happens regularly. First, I was interested to find out if I'm
missing
I'd say that it is C that confused static with constant.
Humans would think of static data as being constant (at least constant once
loaded).
Writeable static is, to me, an oxymoron.
Static is just one of the terms used with computing that is being used with
different meanings. When I
If I have insulted you, please accept my apology,
You have not. It takes much more to do so ;-)
but like many IBM-MAIN members, I try to help for free and when I have
time.
So do I, and I have spent and still do spend much time working with IBM-MAIN
anf other lists. And I have
all languages:
static vs. auto: different allocation technique and time, as already
explained;
static: allocated once, lifetime of the variable is the whole process
auto: allocated on every call of the proc or function, removed at the end
in C: keyword static to denote static variables, no
You don't want to 3.4 delete the data sets, this may cause logger to think the
log stream is damaged.
You'll want to evaluate what is in the log streams and archive the data
appropriately.
See z/OS MVS Setting Up a Sysplex (SA23-1399), Planning for system logger
applications, Deleting log
Bernd Oppolzer wrote:
static vs. auto: different allocation technique and time, as already explained;
static: allocated once, lifetime of the variable is the whole process
auto: allocated on every call of the proc or function, removed at the end
[ ... snipped ... ]
Thanks for your informative
PL/I provides the storage class controlled for implementing anchors
and the like in reentrant routines. C and its sequelæ did/do not, and
this lacuna led to the need for such uglinesses as writable static.
--
John Gilmore, Ashland, MA 01721 - USA
In the OPERLOG, I see the following messages while system CH02PROD is being
shutdown for IPL (more messages in context further down):
N 002 CH02PROD 14333 08:01:23.54 0281 IEA848I DUMP
SUPPRESSED - USER NOT AUTHORIZED BY SAF
N 000 CH02PROD 14333 08:01:23.54
static NEVER means constant
Yip. I believe all wannabee programmers should learn this fact. How difficult
can it be to be understand?
Difficult, if you start as a trainee at a company that decided to force that
all STATIC variables be set to NONASSINGABLE. They very much look like
For IEA848I it says
For USER NOT AUTHORIZED, the security authority can be changed to allow the
application programmer to get the necessary dump by permitting the user to
have READ or UPDATE access to the IEAABD.DMPAUTH facility as described in
the z/OS Security Server RACF Security
Just delete the log stream using the utility and then redefine it.
Rob Schramm
On Jan 17, 2015 9:34 AM, Nick Jones nrjo...@us.ibm.com wrote:
You don't want to 3.4 delete the data sets, this may cause logger to think
the log stream is damaged.
You'll want to evaluate what is in the log
The other area I found of interest:
IGW467I DFSMS RlsAboveTheBarMaxPoolSize 414
D 414 0090 PARMLIB VALUE
CHANGED ON SYSTEM: **ALL**
D 414 0090 OLD
Mark ,
Since you are looking at deleting orphaned logstream datasets , neither TSO
delete or deleting the logstream is going to work
Ane excerpt from MVS setting up a sysplex - Finding and deleting orphaned log
data sets says ,
The orphaned data sets should be deleted using the IDCAMS delete
In PL/I---Things are very different in toy languages like C---the only
legitimate use for static variables is as constants initialized in
their declarations and never altered thereafter. In PL/I it is also
possible to declare and use scalar constants. Thus
declare pi static binary float(53)
For IEA848I it says
For USER NOT AUTHORIZED, the security authority can be changed to allow ...
Thanks for the various tips, Lizette. I'm aware of the FACILITY profile. I'll
have to think about UACC(READ).
The question was how to find the task that triggered the message because it is
26 matches
Mail list logo
