On Tue, 20 Feb 2024 22:58:42 +, Farley, Peter
wrote:
>the monotonically increasing real-time clock to be the “tie breaker” value.
Real-time clocks are not monotonical. Regardless of vendor, there is 1
real-time clock shared by all CPU cores.
> I guess COBOL programmers aren’t supposed
On Thu, 22 Feb 2024 13:45:18 +1000, Peter Vels wrote:
>https://www.ibm.com/docs/en/zos/3.1.0?topic=statement-symlist-parameter
>
I'm looking at Page 263 of SA23-1385-60
z/OS 3.1 MVS JCL Reference
with the page heading DD: SYMLIST
>On Thu, 22 Feb 2024 at 12:46, Paul Gilmartin wrote:
>
>> What
https://www.ibm.com/docs/en/zos/3.1.0?topic=statement-symlist-parameter
On Thu, 22 Feb 2024 at 12:46, Paul Gilmartin <
042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote:
> What does the SYMLIST parameter of the JCL DD statement do?
>
> --
> gil
>
>
For scripting, most recommend Bourne-compatible, which includes BASH,
ZSH, DASH, and [PD]KSH.
In my experience, when you stick with a certain subset of what these all
do you'll be "safe" and your scripts will not break if/when you carry
them around.
I have tried to distill some of the lessons
What does the SYMLIST parameter of the JCL DD statement do?
--
gil
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
The runtime is all part of LE.
Our shop does not have the C/C++ compiler. Never had a business need for it.
Never even looked in to it, so I don't know the cost.
From: IBM Mainframe Discussion List on behalf of
Farley, Peter
No C compiler required. The C runtime is required, but that comes with the OS
(Language Environment).
You bind against SCEELKEX. No Unix required.
From: IBM Mainframe Discussion List on behalf of
Schmitt, Michael
Sent: Wednesday, February 21, 2024 4:19 PM
I need to correct myself. The limit is 16 extents per volume for standard
datasets and for extended it is 123 extents per volume. I guess I was typing
faster than my brain was thinking.
>From the DFSMSdfp Storage Administration manual (z/OS 2.5)
The maximum number of extents per volume and
Michael,
I do not think it requires the C/C++ compiler to use the C RTL subroutines
delivered in CEE.SCEELKEX. You only need the C/C++ documentation to look up
the routine names, though working out how the C "header" files define the
parameters and return value and translating those to COBOL
Our site submitted defrag jobs. Not part of release processing.
On Wed, Feb 21, 2024 at 3:33 PM Ed Jaffe
<05acc3c79bf7-dmarc-requ...@listserv.ua.edu> wrote:
>
> On 2/21/2024 12:52 PM, Gibney, Dave wrote:
> > However, HSM Partial Release should consolidate extents...
>
> Not in my experience.
Well, today was NVIDIA earnings day. They are the bellwether for AI. Theirs is
the premier AI chip commanding top dollar. And they didn’t disappoint. Their
revenues are up 400% in the last year. To 22 billion in the latest quarter.
They’ve got another chip on tap this year which should continue
This requires a C compiler to be installed on z/OS, which doesn't come
standard, correct?
And if you had z/OS XL C, how would you bind this? I mean, is this one of those
things where you're binding against a path on the OEMVS side?
-Original Message-
From: IBM Mainframe Discussion List
DSNTYPE=LARGE allows the 65,535 track (4,369 cylinder) limit to be exceeded.
This should be restricted to SPOOL datasets and the like.
DSNTYPE=EXTENDED does NOT allow this size limit to be exceeded.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Paul Feller
Sent:
Bob, sorry we should have answered some of your questions at the end of your
email
Let me start by saying your storage management team should be able to answer
all your questions. That said I'll answer some of your questions based on what
I know. These are general answers. The SMS
Also, forgot to add: list the dataset and note the management class (MGMTCLAS).
This will tell you how DFSMShsm is managing the dataset and whether space is
routinely being released.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Michael Watkins
Sent: Wednesday,
"ALLOC DDN(CHG$$OT) DSN('') MOD CATALOG REUSE", "SPACE(300,30) CYLINDERS
RECFM(V,B) LRECL(304) BLKSIZE(27998)"
Yes, always allocate anything other than a very small dataset in cylinders.
Also, keep in mind that an extended PS appends a 32-byte suffix onto every
block of data (an 8-byte prefix
At some point in the past, and maybe for greater than n? extents, HSM
accomplished partial release by a migrate/recall under the covers. The may also
be an additional SETSYS needed to enable extent reduction
> -Original Message-
> From: IBM Mainframe Discussion List On
> Behalf Of Ed
On 2/21/2024 12:52 PM, Gibney, Dave wrote:
However, HSM Partial Release should consolidate extents...
Not in my experience. It removes "extraneous" extents (if any), but
doesn't actually do any sort of consolidation of occupied extents.
That said, I believe if you migrate and then later
Its probably doing a release.
Do a cylinder allocation to at average 7 tracks after release.
Defragment to consolidate extents weekly / twice a week / MWF / daily.
On Wed, Feb 21, 2024 at 11:45 AM Bob Bridges
<0587168ababf-dmarc-requ...@listserv.ua.edu> wrote:
>
> I'm not a sysprog (just a
However, HSM Partial Release should consolidate extents, so a properly sized
(big) secondary should keep the abends at bay
> -Original Message-
> From: IBM Mainframe Discussion List On
> Behalf Of Paul Feller
> Sent: Wednesday, February 21, 2024 12:39 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
>
Bob as Steve said you might want to talk to your storge management team. What
I think is happening is your dataset is getting a management class that has
Partial Release set and then HSM is doing space management and releasing any
unused space. I've seen this happen before and it has happened
SMS compression/de-compression is done by the access method
(presuming regular QSAM/BSAM) and is usually transparent to the
application. A long time ago, tailored compression had a bug that
lost track of where the tailored dictionary was kept and
caused abends when trying to read the file.
Ask the storage guys about the preferred method to allocate a
file that will get very large during production runs. And you
don't want production to fail with a storage ABEND. And let them
know about the current behavior. They may have made a change that
is the cause of your problem.
Then
Ooh, now that's interesting! The content of this file would lend itself
well to compression - all alphanumeric with a few parens, colons and the
like. But what happens when someone needs to view it? Does it compress
automatically or is another step required?
It's not something I can bring up
On Wed, 21 Feb 2024 11:32:26 -0600, Joe DeChirico wrote:
>
>Thanks for all the responses, it appears that there was garbage in included
>module, once I removed if from inline and used a ++MOD(VSHMNTSK)
>TXLIB(ZPROTOBJ) . the problem went away.
>
I'm surprised that makes a difference?
How did
Classification: Confidential
The most likely reason is the DATACLAS(? Possibly MGMTCLAS) ACS Routine. This
is where partial space release is specified.
It is possible, but un likely that dfHSM is doing the partial space release.
HSM would be honoring the "dictates" of the DATACLAS.
HTH,
You might consider SMS compression to reduce the physical size of the
file. If you do, change the BLKSIZE to 32760 as SMS compression
writes full tracks and the BLKSIZE becomes logical (the size of the
buffer used in passing date to/from the application).
Michael
At 11:44 AM 2/21/2024, Bob
PS-E (extended format) allows for 123 extents on a single volume. If the
allocated dataset is SMS managed its assigned management class is likely the
reason why free space is being released.
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
I'm not a sysprog (just a security geek), but I can at least allocate datasets,
and at the start of this year it fell to me to allocate a new dataset in which
are logged all changes made in the security system. Past year's log are in the
12000-track range, so I started with a smaller
All,
Thanks for all the responses, it appears that there was garbage in included
module, once I removed if from inline and used a ++MOD(VSHMNTSK)
TXLIB(ZPROTOBJ) . the problem went away.
Joe DeChirico
--
For IBM-MAIN
On Wed, 21 Feb 2024 07:00:23 -0600 Joe DeChirico
<05694ada0b0a-dmarc-requ...@listserv.ua.edu> wrote:
:>I have been trying to package a ptf using smpe and appear to be missing
something, I have attached the job that I submitting Can anyone give me some
idea about what I am doing wrong?
JCL
On Wed, 21 Feb 2024 13:07:24 +, Chalk, Shelia wrote:
>Get rid of the numbers on the right hand side.
>
Why? Those are almost standard..
>... Then resubmit. What error message are you getting?
>
Yes.
I prefer to rely on DDDEFs rather than DD in the JCL.
--
gil
Hi Joe,
Please list the messages too.
Regards,
David
On 2024-02-21 08:00, Joe DeChirico wrote:
Hi,
I have been trying to package a ptf using smpe and appear to be missing
something, I have attached the job that I submitting Can anyone give me some
idea about what I am doing wrong?
> I have been trying to package a ptf using smpe and appear to be missing
> something, I have attached the job that I submitting Can anyone give me some
> idea about what I am doing wrong?
Upon a quick glance nothing is obviously wrong with your JCL. If you show us
the error messages or
Get rid of the numbers on the right hand side. Then resubmit. What error
message are you getting?
Thanks
Shelia Chalk
Mainframe System Programmer
sch...@ssfcu.org
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Joe
DeChirico
Sent: Wednesday, February 21, 2024
Hi,
I have been trying to package a ptf using smpe and appear to be missing
something, I have attached the job that I submitting Can anyone give me some
idea about what I am doing wrong?
--
For IBM-MAIN subscribe / signoff /
https://download.sinenomine.net/hillgang/hillgang-2024-01/Hillgang%202024-01v4.pdf
$*@#*!
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO
With URL to flyer...
The next meeting of “Hillgang”: the DC, Virginia, and Maryland z/VM and Linux
on z User Group will be held on 18 April 2024.
https://download.sinenomine.net/hillgang/hillgang-2024-01/Hillgang 2024-01v4.pdf
Location:
Broadcom/VMware
12100 Sunset Hills Rd
4th FL
Reston VA
38 matches
Mail list logo
