W dniu 2013-08-29 23:09, Ted MacNEIL pisze:
I started as a JCL jockey in Prod Support, under MVS.
It was still supported, then (pre-XA).
-
Supported or just "syntax-checked and ignored" ?
--
Radoslaw Skorupka
Lodz, Poland
--
Treść tej wiadomości może zawierać informacje prawnie chronione
Lizette,
One of the main selling points of the DataDomain is the Global Compression
feature (data deduplication). This works well for multiple backups but not for
archived data which ML2 data effectively is, so in your case using a DataDomain
at the backend would be a very expensive option.
L
W dniu 2013-08-29 23:33, John Gilmore pisze:
The z/OS V1R9 MVS JCL Reference--The 12th edition of 2007 September
and the oldest one I have on my workstation--describes AFF, SEP,
SPLIT, and SUBALLOC as "obsolete subparameters" on page 5-18.
It's still there (at least at z/OS 1.13 level).
However
It seemed to work.
-
Ted MacNEIL
eamacn...@yahoo.ca
Twitter: @TedMacNEIL
-Original Message-
From: "R.S."
Sender: IBM Mainframe Discussion List
Date: Fri, 30 Aug 2013 10:38:57
To:
Reply-To: IBM Mainframe Discussion List
Subject: Re: UNIT=SEP still alive (?)
W
W dniu 2013-08-30 11:50, Ted MacNEIL pisze:
It seemed to work.
-
Tiny Harminc wrote:
"I slightly more than vaguely remember it the same way. SEP=
disappeared (was ignored) with MVS, i.e. OS/VS2 2.0, because it
limited the then-new SRM's ability to swap a job in or out to control
the I/O workloa
I just ran big (huge?) DFSORT job. I had to play with SORTWK space, used
DYNALLOC=(3390,90) and it worked.
90 seems to be much to much, nevermind. However I saw the following
message in the SYSOUT:
ICE118I 0 UNKNOWN FILE SIZE - FILSZ=EN MAY IMPROVE RESOURCE USAGE AND
PERFORMANCE
Note, the input
On Fri, 30 Aug 2013 12:29:47 +0200, R.S. wrote:
> Maybe the above is the answer? Can I provide AVG LRECL or just file size
in bytes?
Yes. OPTION AVGRLEN=n,FILSZ=Ex
Default: If AVGRLEN=n is not specified, DFSORT uses one-half of the maximum
record length as the average record length.
http://pu
Is this question (as it relates to the HC message table) really different
than how do you maintain any load module (or any load module that must be
in the LNKLST)?
I don't pretend to know how that is typically done, but I suspect that in
general it is not considered overly messy.
As was pointed
W dniu 2013-08-30 13:01, Norbert Friemel pisze:
On Fri, 30 Aug 2013 12:29:47 +0200, R.S. wrote:
Maybe the above is the answer? Can I provide AVG LRECL or just file size
in bytes?
Yes. OPTION AVGRLEN=n,FILSZ=Ex
Default: If AVGRLEN=n is not specified, DFSORT uses one-half of the maximum
recor
Tony Harminc wrote:
And on that note, I even more vaguely remember that SEP= (in pre-MVS
OSs) was done at the channel level rather then the device, but that's
so vague as to be unreliable.
and, unlike many such, this particular vague memory is veridical.
SEP= dates back to the early days of OS
On Thu, 29 Aug 2013 12:53:56 -0500, Mike Schwab wrote:
>See below.
>
>On Thu, Aug 29, 2013 at 8:15 AM, Lizette Koehler
> wrote:
>> We are beginning to investigate the possibility of having a DLm and Data
>> Domain tapeless solution in our shop. We are just looking
>>
>> If anyone in a medium to
Peter is correct about checking the status from the SE. If you are running on
a z890/z990 or later, then the machine comes with the CPACF hardware. However,
you have to have FC #3863 installed to enable it. That's how we handle the
export restrictions on crypto technology. If you're from one
On 29 Aug 2013 20:39:00 -0700, in bit.listserv.ibm-main you wrote:
>On Thu, Aug 29, 2013 at 6:25 PM, Clark Morris
>wrote:
>> On 29 Aug 2013 14:33:21 -0700, in bit.listserv.ibm-main you wrote:
>>
>>>The z/OS V1R9 MVS JCL Reference--The 12th edition of 2007 September
>>>and the oldest one I have o
I would like to be able to pass a string to the IBM C/C++ compiler to include
in a program. I have tried every way I can think of to use the DEFINE()
compiler option but can't make it work. This is what I would like to do:
...
// EXEC PGM=CCNDRVR,PARM=('...DEFINE(MYSTRING=TEST)')
...
In the
Unless you have real reel tape drives, or discs with moving heads, most of
these old-time
specs are not valuable (IMHO)...
zNorman
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Clark Morris
Sent: Friday, August 30, 2013 6:45 AM
To:
Hi
In batch I'm using like this:
//COMPILE EXEC PGM=CCNDRVR,REGION=&CREGSIZ,
//PARM=('&CRUN/&CPARM OPTFILE(DD:OPTFILE)')
//STEPLIB DD DSN=&LIBPRFX..SCEERUN,DISP=SHR
// DD DSN=CBC.SCCNCMP,DISP=SHR
//USERLIB DD DISP=SHR,DSN=ESA.PRJ.CBTEXP.HPP
//SYSMSGS DD DUMMY,DSN=&LNGPRFX..S
To close the loop, I think I have beaten MVS and LE into submission! Not
fully tested yet ...
The short version is that the first (or only) save area back pointer must
not be zero but rather = CEECAADDSA. Also I changed a line in the code I
originally posted to
AUTO=5000, A
While SEP is certainly obsolete in the world of virtual disk, AFF is very
much required in cases where many--perhaps dozens of--tape files are to be
read in a single step. MVS does not know from virtual, so he wants to
allocate 25 drives to read 25 tape volumes unless constrained by AFF.
Althou
I have the following log stream defined:
LOGSTREAM NAME(HZS.HEALTH.CHECKER.HISTORY) STRUCTNAME(HZS_HEALTHCHKLOG)
LS_DATACLAS(LOGSTRM)
LS_MGMTCLAS(NOMIG) LS_STORCLAS(BASE) HLQ(IXGLOGR) MODEL(NO)
LS_SIZE(4096)
STG_MGMTCLAS() STG_STORCLAS() STG_DATACLAS() STG_SIZE(0)
Where is that LOGSTREAM command? When I tried to look up the LOGSTREAM
RETPD parameter, it said it was a REGISTER which contained a 4 byte value
for the number of days. At first glance, your command would seem to want
2 day retention period, but if it is really referencing REGISTER 2, then
who
Hi Dave,
I don't know what the web pages on the customer end of the SR process look
like, but I guess my expectation would be that there would be a check box
somewhere for "notify" or something similar. If there is not, then
another way to go is to say that email is your preferred method of conta
On 8/30/2013 11:55 AM, Joel C. Ewing wrote:
A highly counter-intuitive case for many new users used to be the case
of a DDNAME with concatenated tape data sets, where the data sets are
obviously constrained to access in sequential fashion; but the MVS
default (without UNIT=AFF) was to allocate
I haven't seen this problem except when logger is sick. OTOH we use system
logger for other functions: SMF, Operlog, CICS logs. I'm not sure what
makes these puppies go away on a regular basis, but I also thought the
combination of RETPD and AUTODELETE would make them disappear. If a log
stream
Ed,
Try a LIST LOGSTREAM NAME(HZS.HEALTH.CHECKER.HISTORY ) DETAIL(YES) in that
same IXCMIAPU to get an inventory of what logger really knows about. If file is
NOT there then it is orphaned.
Dennis
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] O
On 8/30/2013 10:49 AM, Roger Bolan wrote:
Where is that LOGSTREAM command? When I tried to look up the LOGSTREAM
RETPD parameter, it said it was a REGISTER which contained a 4 byte value
for the number of days. At first glance, your command would seem to want
2 day retention period, but if it
On Fri, 30 Aug 2013 09:54:55 -0700, Ed Jaffe
wrote:
>I have the following log stream defined:
>
>LOGSTREAM NAME(HZS.HEALTH.CHECKER.HISTORY) STRUCTNAME(HZS_HEALTHCHKLOG)
>LS_DATACLAS(LOGSTRM)
> LS_MGMTCLAS(NOMIG) LS_STORCLAS(BASE) HLQ(IXGLOGR) MODEL(NO)
>LS_SIZE(4096)
> STG_MG
They may be orphans
Can you please show us the listing of:
DATA TYPE(LOGR) REPORT(NO)
LIST LOGSTREAM NAME(HZS.HEALTH.CHECKER.HISTORY) DETAIL(YES)
Regards,
Leo
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Ed Jaffe
Sent:
Roger Bolan wrote:
At first glance, your command would seem to want 2 day retention
period, but if it is really referencing REGISTER 2, then who knows
what value you're getting.
Who indeed! This is a truly drôle suggestion. Taken seriously, this
facility is ill-conceived in detail. A registe
On 8/30/2013 9:54 AM, Ed Jaffe wrote:
I assumed that RETPD(2) and AUTODELETE(YES) would keep the number of
health checker data sets to a minimum, but there is a space explosion
of literally thousands of IXGLOGR.HZS.** data sets--with the oldest of
them allocated last year:
My attempt to manua
On Fri, 30 Aug 2013 13:16:58 -0700, Ed Jaffe
wrote:
>On 8/30/2013 9:54 AM, Ed Jaffe wrote:
>> I assumed that RETPD(2) and AUTODELETE(YES) would keep the number of
>> health checker data sets to a minimum, but there is a space explosion
>> of literally thousands of IXGLOGR.HZS.** data sets--with
We had one in early XA ESP where techy changed a few jobs and had UNIT=3800 for
SORTWKs and it tried to honor it. Can you say wreck?
In a message dated 08/30/13 13:23:33 Central Daylight Time, gerh...@valley.net
writes:
He reported that a "CoBOL" programmer submitted a sort job with
all sor
On 8/30/2013 1:25 PM, Mark Zelden wrote:
BTW, why only RETPD 2 days? These data sets aren't that big and every once in
a while I find it very useful to print the history for a check. I have mine
set up for 14 days even in my sandboxes.
It was originally set for RETPD(7). When we first starte
On 08/30/2013 08:44 AM, Clark Morris wrote:
> On 29 Aug 2013 20:39:00 -0700, in bit.listserv.ibm-main you wrote:
>
>> On Thu, Aug 29, 2013 at 6:25 PM, Clark Morris
>> wrote:
>>> On 29 Aug 2013 14:33:21 -0700, in bit.listserv.ibm-main you wrote:
>>>
The z/OS V1R9 MVS JCL Reference--The 12th
There were check boxes, I included the options in my original note.
Getting an email was not one of the options.
I either had to look periodically, or say call me at a phone number.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Roge
works fine with definition in OPTFILE DD:
//COMPILE EXEC PGM=CCNDRVR,
//PARM=('/CXX OPTFILE(DD:CCOPT)')
//CCOPTDD DATA,DLM=##
DEFINE(MYSTRING="MICHAEL")
SEARCH('CEE.SCEEH.+','CBC.SCLBH.+')
OPTIMIZE(2)
##
trying same with parm card, I also failed with messages you described.
C
There are sorting algorithms the performance of which is a simple
linear function of R, the number of records sorted; but you do not
want to use them.
Respectable sorting algorithms on the other hand, are faster, often
much faster, for ordered-in-part data than they are unordered data.
(A simple b
Are the keys the same? Is there a difference in how out-of-order each file
is going into the sort?
> There is no difference in the parameters given via PARM and/or SYSIN
Must be a different sort key, right? Or what's the point? Is each sort
sequence the same? If you sort a file into a particular
While analyzing high CPU consuming jobs we came across a peculiar behavior of
SYNCSORT. Certain SYNCSORT steps in some of the jobs are *regularly* (not just
occasionally) taking much more time than some of the other SYNCSORT steps in
the same jobs with same amount of data. For example, in one j
You're right, the sort orders are not the same. For the CPU example I gave
below, the first sort uses these parameters:
$ORTPARM: CORE=MAX
SYSIN: SORT FIELDS=(1,3,CH,A,17,7,CH,A)
The second one gets these:
$ORTPARM: CORE=MAX
SYSIN: SORT FIELDS=(1,24,CH,A)
The application in ques
Hard to say without knowing data patterns. Alt indexes can speed things up a
lot
another is interchange sort order and take Sortout of Long sort(1-24) and feed
into
the short sort 1-3,17-24.
In a message dated 08/30/13 17:22:10 Central Daylight Time,
peter.far...@broadridge.com writes:
You'
In
,
on 08/30/2013
at 12:38 AM, Tony Harminc said:
>There is a widespread and hard to break culture consisting of some
>blend of "if it ain't broke, don't fix it", "I'll just copy this
>JCL that works and change it minimally to suit my needs",
Not just JCL, and normally without the analysis
Peter,
John's initial guess was pretty much on target. You first sort is going to do
much more work than the second one. You might ask why since it is sorting on
fewer key bytes?
The answer is they share the first 3 bytes, which might not seem like much, but
it at least groups the data. Let
On 30 Aug 2013 16:13:59 -0700, in bit.listserv.ibm-main you wrote:
>Peter,
>
>John's initial guess was pretty much on target. You first sort is going to do
>much more work than the second one. You might ask why since it is sorting on
>fewer key bytes?
>
>The answer is they share the first 3 by
At 14:23 -0400 on 08/30/2013, Gerhard Postpischil wrote about Re:
UNIT=SEP still alive (?):
This appears to be a no-win situation for IBM. Our systems used AVR, and
had enough drives, so that for us it was more important to reduce tape
mount delays (while the job sat occupying limited storage).
On Fri, 30 Aug 2013 09:15:28 -0500, Mark Hammack wrote:
>I would like to be able to pass a string to the IBM C/C++ compiler to include
>in a program. I have tried every way I can think of to use the DEFINE()
>compiler option but can't make it work. This is what I would like to do:
>
>...
>//
On 8/30/2013 9:22 PM, Robert A. Rosenberg wrote:
I know for multi-volume datasets UNIT=(TAPE,2) handled the mount of
volume3 while volume1 rewound and unloaded. I do not remember if you
could allocate 2 units and have concatenated input volumes alternate
between them. AVR might have helped since
46 matches
Mail list logo
