Hello John,
I have been reading my digest copy of yesterday's posts and found a bunch
of similar replies.
I will not assume that you can actually access ISPF EDIT on your mainframe.
If you do and you edit the JCL you most likely wont know that in columns 73-
80 there may be line numbers. The
On Sat, 2006-07-29 at 00:40 -0500, Bill Seubert wrote:
When we can connect customers who have
skill issues to the universities from which they hire students, ...
Excuse my sceptocity, but such customers exist ???
From my perspective, seems that customers are more willing to hire
expertise than
Ted MacNEIL wrote:
Did it ever occur to you that the same is true for using USS when you don't
mean USS?
Give it a rest!
Even IBM calls it USS.
The weight of the world must not be on your shoulders if you have nothing to
worry about besides a silly anacronym.
Ted,
Calm down, it is not
Ted MacNEIL wrote:
HSA is currently at 128mb. All main is allocated, no slop anywhere. If HSA grows, then I'll lose an LPAR.
128MB is nothing for HSA, these days.
If you are so tight that an increase to such a small HSA is an issue, you have
a bigger problem than the size of HSA!
At
Marc Holiwell wrote:
I am currently running two LPARs (with zOS 1.4 as OSes)
on a IBM 2086 model A04(220), and would like to know
if it is possible to create an IOCDS that will support
an LPAR with VM as the OS, and another LPAR with
zOS as the OS...???
As other already mentioned, LPAR
Paul Gilmartin wrote:
In a recent note, Shmuel Metz (Seymour J.) said:
Date: Fri, 28 Jul 2006 16:57:30 -0300
That said, others have told you about UNNUM; that will indeed delete
those sequence numbers, which in fact are not annoying.
It appeared to me that the OP, perhaps using
Calm down, it is not worth to worry about.
Actually, I was calm!
It just seems that some people can't take a hint,
so I raised the tone of my response.
Schmeul, nobody wants to hear it!
BTW, I'm taking the kill file route, too.
So, respond if you like, I won't see it!
When in doubt.
PANIC!!
These days, I would plan for a minimum of 1GB HSA, and a minimum of 3 per
LPAR.
More if it's doing real work (DB2, IMS, or CICS).
Wrong plans IMHO. HSA size strongly depends on CPC generation. Before
z/990 (that means 9672, z/900, z/800) HSA size was related to IODF size
- number of
R.S. wrote:
Paul Gilmartin wrote:
In a recent note, Shmuel Metz (Seymour J.) said:
Date: Fri, 28 Jul 2006 16:57:30 -0300
That said, others have told you about UNNUM; that will indeed delete
those sequence numbers, which in fact are not annoying.
It appeared to me that the OP,
On Friday 28 July 2006 23:47, Steve Myers wrote:
At step end, the initiator will DEQ any DSNs that are no longer
needed, i.e. those which are not referenced on a DD in any later
step.
This change was fairly recent. Originally, the data set ENQ lasted
for the life of the job. I do not
When IBM migrated our DASD from 2105 to 2107 1st Q this year (on a
2064-106), FDRPAS is the tool they brought with them. CPU use by FDRPAS
was not an issue - device activity and channel activity could be,
especially if you have any specific devices that are already showing up
as a performance
In a recent note, R.S. said:
Date: Sat, 29 Jul 2006 12:42:19 +0200
Perhaps you feel that all utilities, on all platforms, should
process only columns 1-72 of their input data. Ain't gonna
happen.
Even some mainframe programs interpret it as data, with funny effects
somtimes.
AFAIK the sequence numbers are completely useless nowadays. It was used
for punched card sorter. Is there any other application ?
OK. Anyone who agree with the above statement is no longer allowed to use
++MACUPT or ++SRCUPD in SMP or to ever use IEBUPDTE.
Granted, these are very special,
SNs were useful when cataloged procedures and source programs were
maintained using such batch edit utilities as IEBUPDTE and IEBUPDAT.
Their current uses are exiguous; they are of only antiquarian interest; and
even that interest has, it seems to me, been exhausted.
John Gilmore
Ashland, MA
I just installed wd4z 6.01. Having trouble starting the JES Jmonitor on the
default port of 6715 on a zos 1.6 system. It works on a test 1.7 system.
It starts ok if the port number is 3 digits, but not when it is 4 digits.
Anyone have any ideas?
Thanks,
Mary Kay
In a message dated 7/29/2006 5:42:36 A.M. Central Standard Time,
[EMAIL PROTECTED] writes:
AFAIK the sequence numbers are completely useless nowadays. It was used
for punched card sorter. Is there any other application ?
Your PARMLIB and a few others are maintained by SMP/E with
Mary Kay Tubello wrote:
I just installed wd4z 6.01. Having trouble starting the JES Jmonitor on the
default port of 6715 on a zos 1.6 system. It works on a test 1.7 system.
It starts ok if the port number is 3 digits, but not when it is 4 digits.
Anyone have any ideas?
Thanks,
Mary Kay
Do
Several hours ago, I had entered a nice email on this topic that was running
under the subject of: Re: IBM Redbook: Introduction to the New Mainframe:
z/OS Basics . Since I spent about 10 minutes composing it, the **^% web
site that I use to read IBM-Main on my laptop timed out. Usually, I
john gilmore wrote:
SNs were useful when cataloged procedures and source programs were
maintained using such batch edit utilities as IEBUPDTE and IEBUPDAT.
Their current uses are exiguous; they are of only antiquarian interest;
and even that interest has, it seems to me, been exhausted.
I have been burned in the past by the syntax for OPEN and CLOSE not
being identical. You have an extra pair of parentheses in your CLOSE
which I believe is causing the macro to interpret your DCB address as
being an expression (R3) rather than a register reference, which would
mean it would
On Fri, 28 Jul 2006 17:16:44 -0400 Wayne Driscoll [EMAIL PROTECTED]
wrote:
:While that is true, since non-reentrent code loaded out of an APF
:authorized library is loaded into KEY 8 storage, there is an integrity
:exposure if said code is loaded into a multi-user address space, since
:it is open
Their current uses are exiguous; they are of only antiquarian interest; and
even that interest has, it seems to me, been exhausted.
REPEAT AFTER ME!
SMP is your friend!
SMP NEEDS statement numbers.
When in doubt.
PANIC!!
Ted MacNeil WRITES:
REPEAT AFTER ME!
SMP is your friend!
SMP NEEDS statement numbers.
SMP certainly uses SNs and IEBUPDTE in some contexts. Equally, it omits to
use them in others where it could do so.
It never needs to use them, and it would be well if it had stopped doing so
long
John,
While your statement is true it would seem to me JES2 (JES3?) still
sends out source and as long as it does then statement sequence
numbers are needed. I vaguely remember that IBM at one time said they
were going to stop sending out source for the JES's. They have done
this with
Ed Gould wrote:
While your statement is true it would seem to me JES2 (JES3?) still
sends out source and as long as it does then statement sequence
numbers are needed. I vaguely remember that IBM at one time said they
were going to stop sending out source for the JES's. They have done
this
Oh, the hazards of working without coding examples and manuals at hand!
Obviously I've suffered a memory parity error and the peculiar
failures in the past that I'm thinking of must have been from using
CLOSE (R3) rather than CLOSE ((R3)), which I confirmed does indeed pass
the contents of
26 matches
Mail list logo
