Hi
Thank you.
In the current SMF 70% of the records is 92, USS activity and 25% DB2
I will try without this ( see the speed) and maybe send 92 to a
different stream.
In the stream we have currently about 50 Mbyte data and the access here
10-20 seconds
to retrieve all the SMF records for a
Hello
I need to archive about 120.000 files and delete the Originals.
What I wanted to do is:
1. to create a new MGMTCLAS with following Parms:
Backup frequency . . . . . . . . . . . : 0
Number of backup versions . . . . . . . : 1
(Data Set
Exists)
Hi
If you issue a REXX readdir, in the optional stem2 you got the fstat
structure
I'm using from this the st_ctime and st_mtime and convert via the
gmtime function
On 01.06.2012 21:54, Roger Wasley wrote:
Afternoon
I have been attempting to use SYSCALL READDIR and the fstat according to
On Sun, 3 Jun 2012 11:47:23 -0500, Paul Gilmartin paulgboul...@aim.com wrote:
Should I infer from this that conversely it runs concurrently
in background and does not tie up the terminal if output is
directed to SYSOUT or ODS? If so the above EXEC needs a
WAIT to guarantee that the output is
Ouch. Doing that sort of polling makes me cringe. And inspires an idea (perhaps
insane). Write an APF authorized TSO command which can do an ISGENQ on any
QNAME / RNAME (even a restricted one) with the WAIT option. When acquired,
immediately release the ENQ and exit. It might even have a
The subject is the question. Obviously I can insert a WORKING-STORAGE switch
that is off by default and a Debugging line in the PROCEDURE division to turn
on that switch when WITH DEBUGGING is in effect, but this seems clumsy to
me.
If there is another way, I'd appreciate any info you can
I don't know of a way to detect that via an API call. I am curious as to why
you want to. Seems inefficient to me. The compiler knows at compile time if
WITH DEBUGGING is ON or OFF. So why use up CPU cycles determining something
that is already determined at compile time. Whatever you are going
John,
Thanks for clearing my mind on this. You're right, it really is not something
I should do, since as you say the code with Debugging marks in column 7 is
either there or not there after the compile is done. I think I was trying to
provide for dynamically (perhaps via PARM) controlled
Hum, I just thought of one reason why you might want to do this. That is if you
want to __NOT__ do something if debugging is OFF. In HLASM, I use AIF, but I
can do a NE test. In COBOL, there is not a character in column 7 to indicate
do not compile if debugging is OFF. I did think of a
Could you have a switch that was set to 'X' by default but to 'Y' by a
debugging statement, and then your if not debugging test is switch NE 'Y'.
Do we really need to care about CPU cycles for a debugging IF?
Charles
-Original Message-
From: IBM Mainframe Discussion List
Most probably do not care. We do. You'd be amazed at the things we do to reduce
our MSU requirements. Programmers are a fixed cost. From what I've been told,
if we could reduce our Group Capacity by 1 MSU, we would save $13,000/yr, in
hard dollars. So we would spend many soft dollars to do
Takes a lot of IF statements to equal one MSU.
Does not take a heck of a lot of programmer time to equal $13,000.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf
Of McKown, John
Sent: Monday, June 04, 2012 1:05 PM
To:
$13,000 in soft dollars is infinitely more than $13,000 in hard dollars.
And the takes a lot of IF statements to make one MSU is true. And we execute
a LOT of IF statements, when aggregated across all executions of all programs
in a year.
In theory, I agree with you. In a shop which is more
I hear you. Keep the faith. Good luck.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf
Of McKown, John
Sent: Monday, June 04, 2012 2:11 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Is there an Enterprise COBOL API to detect
How about a LINKAGE SECTION to access the parm
//STEPNAME EXEC PGM=program,PARM='' or
//STEPNAME EXEC PGM=program,PARM='DEBUG'
Inside the program,
LINKAGE SECTION.
01 PARM-ALL.
05 PARM-LENGTH PIC S9(4) COMP.
05 PARM-DATA.
10 PARM-BYTE PIC X OCCURS 0 TO 100 DEPENDING ON PARM-LENGTH.
PROCEDURE
On Mon, Jun 4, 2012 at 12:11 PM, Farley, Peter x23353
peter.far...@broadridge.com wrote:
The subject is the question. Obviously I can insert a WORKING-
STORAGE switch that is off by default and a Debugging line in the
PROCEDURE division to turn on that switch when WITH DEBUGGING is
in
Peter,
We pass a parm debug=y or debug=n , our code there is a 88 level...
If debug-on
...
...
End-if
Plus I had to create a special sysout , allocated dynamically...
Scott ford
www.identityforge.com
On Jun 4, 2012, at 1:11 PM, Farley, Peter x23353
peter.far...@broadridge.com wrote:
17 matches
Mail list logo