Phil and Mike,
Yep..but which of the PC vendors , for example, write for older machines? Most
of the products require a bigger footprint, either in memory or HDD space. Z/os
a different story as far as I am concerned
Scott ford
www.identityforge.com
from my IPAD
'Infinite wisdom through
I just noticed this insert added to msgIXC334I by OA41210:
SYSPLEX INITIALIZATION TIME: 12/29/2011 20:59:16.385348
So this sysplex is about 1 1/2 years old. Are there production sysplexes
that are decades old?
--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El
What is the character between the two single quote marks in the first call
to memset? My email shows no character (the quotes are adjacent) and C does
not support an empty character constant. Perchance did you have a hex 00
there? If so, the code would be more readable using '\0' as the
You mentioned in passing the problem with debugging Metal C by adding printf's.
Unfortunately, Metal C does not offer I/O functions. I solved this problem by
writing an extension library with basic I/O support.
Tony
--
For
Hi,
Not proffecient in CLISTS and RExx.
Can I get some assistance with examining testing a return code in a CLIST
Macro.
In A CLIST i execute the following statements to edit a member of a PDS
and use the ALTER MACRO to change all occurances of XXX.
SET IOFUNC = STR(EDIT)
On Sat, 11 May 2013 12:25:13 -0700, retired mainframer wrote:
What is the character between the two single quote marks in the first call
to memset? My email shows no character (the quotes are adjacent) and C does
not support an empty character constant. Perchance did you have a hex 00
there?
The edit session ends with CANCEL, which means no changes were saved, which
means ISPF sets the return code of the macro to 4. If you want to end with a
different return code, you can hard code it like this:
EXIT CODE(0)
Or set it using this as an example:
ISREDIT CHANGE 'XXX' 'V0' ALL
6 1/2 years here
On 11 May 2013 15:04, Ed Jaffe edja...@phoenixsoftware.com wrote:
I just noticed this insert added to msgIXC334I by OA41210:
SYSPLEX INITIALIZATION TIME: 12/29/2011 20:59:16.385348
So this sysplex is about 1 1/2 years old. Are there production sysplexes
that are decades
Your edit macro ALTER performs two different functions: it changes all
occurrences of one string to another and submits a job. Either of these
could fail. Which would you like the return code to reflect?
You could initialize a local variable to 0 near the top of your macro.
After issuing the
I'll see your 6.5 years and raise you!
SYSPLEX INITIALIZATION TIME: 02/24/2004 23:46:17.566318
Andrew
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Graham Harris
Sent: 11 May 2013 22:52
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re:
Hello,
NQ: Trying to keep my SD;O list short. I find 15 of the following thereon:
SYSLOG STC2 +MASTER+ 144 C STD LOCAL 70
SYSLOG STC00018 +MASTER+ 128 C STD LOCAL 3,536
SYSLOG STC00052 +MASTER+ 128 C
Graham,
Syslog is a log and history of what has been going on in your system. Jobs
that have run, messages written to syslog, etc...
Some shops archive it to dasd as a GDG to keep it around in-case they need
to go back and research an issue.
So the choices are
1) Leave it on spool
2) Write
On Sat, 11 May 2013 17:09:19 -0400, Dave Salt wrote:
The edit session ends with CANCEL, which means no changes were saved, which
means ISPF sets the return code of the macro to 4. If you want to end with a
different return code, you can hard code it like this:
EXIT CODE(0)
Or set it using this
Does your suggestion leave the file unchanged, end the edit session
with RC=0, and not leave the user in a terminal edit session?
The edit session would end with whatever return code was set by CHANGE. For
example, if the change was successful (RC=0, which means one or more strings
were
14 matches
Mail list logo
