Shmuel Metz (Seymour J.) wrote:
TSO is supposed to allocate SYSUT3 and SYSUT4,
There's nothing special about SYSUT3 and SYSUT4. TSO allocates whatever is in
the logon proc.
Very True! Before issueing 'Z' in =3.4 or 'C' in =3.1, you can use ISRDDN to
see if you have SYSUT3/4 allocated or not.
Bernd Oppolzer wrote:
I found the Repair program for the PO Archive; it is from March 2001.
It is very kind of you to post it here.
There are two drawbacks:
- the comments are in German language
Good. It is not a drawback for me. ;-D
From RECFM=VB,
to RECFM=FBA,
Very interesting that you
Hi,
Does anyone know why on z/OS in include file atbcmc.h the APPC functions
CMSCST, CMSCSU and CMSCSP have been commented out for MVS?
#if defined(CM_OS400) || defined(CM_MVS)
/* pragma linkage (CMSCSP, OS)
@04C */
/* pragma linkage
try this link:
http://publib.boulder.ibm.com/infocenter/zos/basics/index.jsp?topic=/com.ibm.zos.zsysprog/zsysprogc_searchorder.htm
This information is probably accurate as far as it goes, but it could go
further.
I go here for this information:
Title: z/OS V1R13.0 MVS Assembler Services Guide
I'm reworking some code to avoid multiple OPENs for
reading PDS members..
But, I will still be just reading one member at a time,
and I don't know the member names a-priori.
The DFSMS documentation states that using BLDL + FIND
(and using the ttr,C form for FIND) results in a performance
On Mon, 25 Mar 2013 09:01:55 -0500, John McKown wrote:
(You! of all people!)
Have you looked at the newer DESERV macro? It can fetch the entire
directory of a PDS or PDSE in one gulp. ...
ref:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/dgt2d490/3.8.7.4.2
quote
3.8.7.4.2
Good point. The OP didn't mention whether a z/OS UNIX directory was a
possibility or not. If so, then DESERV likely isn't the way to go. Of
course, for me, if I want to support z/OS UNIX, I'd do it natively not
using BPAM emulation (which is OK I guess, but ugly).
On Mon, Mar 25, 2013 at 9:11
How would this be possible? Image A looks at database A for access rules. Image
B looks at database B for access rules.
Even if they are the same name, they cannot be cataloged concurrently. i.e.
each must exist in a separate catalog.
What would cause the exposure?
snip
Do you share the
(I was on vacation; I cannot speak for why the consoles team has not
responded).
OA36338 was mentioned.
But beyond that, any thought about during IPL vs after IPL will not
apply.
Exit processing in this case is
-- anything defined via the PROGxx processed during IPL is in limbo for
a while.
On Mon, 25 Mar 2013 09:15:01 -0500, John McKown wrote:
Good point. The OP didn't mention whether a z/OS UNIX directory was a
possibility or not. If so, then DESERV likely isn't the way to go. Of
course, for me, if I want to support z/OS UNIX, I'd do it natively not
using BPAM emulation (which is
Since z/OS about 1.4 or 1.5, JES2 has supported instream data
sets with RECFM=VB and LRECL80; up to at least a few hundred.
(This facility is much older in JES3.) I've found it useful at times;
it much simplifies the task of formatting input data. And it has
been (pre-)announced that z/OS 2.1
Hi guys...I have been asked to do some COBOL coding, and I have not done
some for quite a few years. Is there a COBOL listserv available, and is
there any other website that would have recommended best practices?
For example, I used to try to code all my working storage under a very few
01
Thanks to everyone for the responses (Allan, Mike, Barbara, Mark and Doug).
But first: Have you checked the archives? Most of the checks you talk about
here I have complained about in the past. Documented in the archives.
Yes. But, when I saw your question, I've searched even more thoroughly,
My opinion on your level question. 01 level is generally used to group
together related storage or variables. Each 01 level starts a new storage
area on a doubleword boundary. 77 levels are generally used for
independent variables such as loop counters or maybe accumulators of some
sort.
On Mon, 25 Mar 2013 09:46:56 -0400, Thomas David Rivers wrote:
I'm reworking some code to avoid multiple OPENs for
reading PDS members..
But, I will still be just reading one member at a time,
and I don't know the member names a-priori.
The DFSMS documentation states that using BLDL + FIND
(and
Sorry. finger check before I ended the last IF
IF condition THEN
IF cond2
THEN statement
END-IF
ELSE
else for first condition
END-IF
Or maybe something as weird as:
COMPUTE A=B+C/D*F
ON SIZE ERROR
DISPLAY 'GOT SIZE ERROR COMPUTING A' UPON SYSOUT
GOBACK
END-COMPUTE
On Mon, Mar 25,
On 3/25/2013 9:17 AM, Bill Ashton wrote:
Hi guys...I have been asked to do some COBOL coding, and I have not done
some for quite a few years. Is there a COBOL listserv available, and is
there any other website that would have recommended best practices?
For example, I used to try to code all my
If, as seems likely, you are going to read a significant number of
members from the same PDS[E], then the DESERV macro is likely to yield
better performance (and a simpler program) than BLDL either above or
under the covers. This would also be the case if you had occasion to
read the same member
Bill Godfrey wrote:
On Mon, 25 Mar 2013 09:46:56 -0400, Thomas David Rivers wrote:
I'm reworking some code to avoid multiple OPENs for
reading PDS members..
But, I will still be just reading one member at a time,
and I don't know the member names a-priori.
The DFSMS documentation states
On Mon, 25 Mar 2013 11:19:47 -0500, John Gilmore wrote:
If, as seems likely, you are going to read a significant number of
members from the same PDS[E], then the DESERV macro is likely to yield
better performance (and a simpler program) than BLDL either above or
under the covers. This would also
3 of the 4 sessions presentations are available at
https://www.sinenomine.net/node/902
Neale
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO
The clearest exposure is that different systems (LPARs) performing
different enterprise roles may well treat like-named data sets
differently. For example, if SYSA is a development/test/sandbox system
while SYSB is a production system, the access rules on SYSA may well be
much looser in
On Mon, 25 Mar 2013 12:28:00 -0400, Thomas David Rivers wrote:
Bill Godfrey wrote:
On Mon, 25 Mar 2013 09:46:56 -0400, Thomas David Rivers wrote:
I'm reworking some code to avoid multiple OPENs for
reading PDS members..
But, I will still be just reading one member at a time,
and I don't know
Hi all,
I have some temporary files not deleted. Seen with 3.4 with volume given. When
i tried to delete them , i had an error message (entry not found)
Listcat gave this :
LISTCAT ENTRIES(SYS12048.T104505.RA000.IBMUSER.R018)
IDC3012I ENTRY
On 3/25/2013 8:06 AM, Paul Gilmartin wrote:
So, in 2.1, will I be able to use RECFM=VB and long records in
instream data sets in instream procs? Will I be able to define
JCLLIB with RECFM=VB to support such instream data sets
there?
I gotta ask. Why not just try this yourself? You no longer
You do not mention whether the volume/dataset are SMS managed (or not).
DELETE FILE in idcams only uses the DD statement for volume/vvds access. It is
essentially trying to do a normal delete (including the catalog update).
IEFBR14 does not care if the dataset is cataloged or not. It merely
DSN not Catalogued.
-
Ted MacNEIL
eamacn...@yahoo.ca
Twitter: @TedMacNEIL
-Original Message-
From: Ducky duke ndt@gmail.com
Sender: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU
Date: Mon, 25 Mar 2013 12:49:46
To: IBM-MAIN@LISTSERV.UA.EDU
Reply-To:
On Mon, 25 Mar 2013 11:03:25 -0700, Ed Jaffe wrote:
On 3/25/2013 8:06 AM, Paul Gilmartin wrote:
So, in 2.1, will I be able to use RECFM=VB and long records in
instream data sets in instream procs? Will I be able to define
JCLLIB with RECFM=VB to support such instream data sets
there?
I
In my z/OS 1.11 copy on line 999 there is a comment that states they are not
supported by APPC/MVS.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
On Behalf Of Etienne Thijsse
Sent: Monday, March 25, 2013 6:09 AM
To: IBM-MAIN@LISTSERV.UA.EDU
On Mon, 25 Mar 2013 10:31:48 -0500, I P ip4w...@gmail.com wrote:
Thanks to everyone for the responses (Allan, Mike, Barbara, Mark and Doug).
Check: GRS_CONVERT_RESERVES
It seems it's still unclear is converting reserves + proper RNL exclusions
enough.. Also, is it worth it performance wise?
At 12:49 -0500 on 03/25/2013, Ducky duke wrote about Dataset DELETE
question : IEBFR14 vs IDCAMS:
Hi all,
I have some temporary files not deleted. Seen with 3.4 with volume
given. When i tried to delete them , i had an error message (entry
not found)
Listcat gave this :
LISTCAT
Actually, the missing NVR (NonVsam Record) as suggested by Allan should have
accomplished the task. It basically tells IDCAMS not to fail if the Catalog
record is missing.
Dave Gibney
Information Technology Services
Washington State University
-Original Message-
From: IBM Mainframe
You may not even have security rules in place on the foreign system
(accessing) than the native system (creator). I. E. a production HLQ
that is not defined on the test system. You could set Security to not
allow access to datasets without a security definition.
On Mon, Mar 25, 2013 at 12:08
On Mon, 25 Mar 2013 14:38:41 -0400, Steve Thompson wrote:
Now, go whack the person that wrote the JCL that has the following
similarly coded DD statement:
//SYSUT3 DD UNIT=3390,SPACE=(CYL,10),DISP=(NEW,CATLG)
This is what produces a data set name like this:
W dniu 2013-03-25 19:55, Mike Schwab pisze:
You may not even have security rules in place on the foreign system
(accessing) than the native system (creator). I. E. a production HLQ
that is not defined on the test system. You could set Security to not
allow access to datasets without a security
On 3/25/2013 11:13 AM, Paul Gilmartin wrote:
On Mon, 25 Mar 2013 11:03:25 -0700, Ed Jaffe wrote:
I gotta ask. Why not just try this yourself? You no longer work for
an ISV?
I still work for an ISV. I hadn't thought to ask whether we have 2.1. And if
I do find out, I won't be allowed to say
On 3/25/2013 12:18 PM, Ed Jaffe wrote:
The existence of ISV Early Programs is no secret:
http://dtsc.dfw.ibm.com/MVSDS/'HTTPD2.DSN01.PUBLIC.PDF(ISVEPROG)'
Note: Some browsers might not like the apostrophes in this URL. You
might have to hand-paste or hand-correct the URL it to read this
Gil and Steve (and probably others who feel the same way),
Before you get too whack-happy, there are other reasons why something like this
could show up. At some point in the deep, dark past, if the system fell over
for whatever reason (power outage, operator - or sysprog - error that caused
On 2013-03-25 13:44, Pommier, Rex R. wrote:
Gil and Steve (and probably others who feel the same way),
If IBM has added a cleanup routine, or if it is found that some poor JCL
coder did code a DISP on a temporary dataset, then by all means, whack away.
:-)
I often code (,PASS), and I
From: Pommier, Rex R. rex.pomm...@cnasurety.com
Date: 03/25/2013 03:49 PM
Gil and Steve (and probably others who feel the same way),
Before you get too whack-happy, there are other reasons why something like
this could show up. At some point in the deep, dark past, if the system
fell
For people and institutions which owned or managed bonds, Y2K occurred
1/1/1970. Right after that Warrington had a nifty package which I
supported for a while for a bank in Houston which had all 4 digit yrs.
On the other hand the bank's DDA internally written code stored the yr as
1/2 byte so
On Mon, 25 Mar 2013 14:00:49 -0500, Paul Gilmartin wrote:
On Mon, 25 Mar 2013 14:38:41 -0400, Steve Thompson wrote:
Now, go whack the person that wrote the JCL that has the following
similarly coded DD statement:
//SYSUT3 DD UNIT=3390,SPACE=(CYL,10),DISP=(NEW,CATLG)
Has this ever been
IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU wrote on
03/17/2013 05:05:59 AM:
From: Shmuel Metz (Seymour J.) shmuel+...@patriot.net
In 514527e5.3030...@acm.org, on 03/16/2013
at 09:18 PM, Joel C. Ewing jcew...@acm.org said:
All the focus on early memory prices also glosses
Tested the delete with IDCAMS NVR option, doesn't work .. do i miss something
?
(WORK03 is SMS managed)
/STEP010 EXEC PGM=IDCAMS
/SYSPRINT DD SYSOUT=*
/DD01 DD DISP=OLD,VOL=SER=WORK03,UNIT=3390
Does anyone know if I can create an instream entry that would be used as an
INCLUDE? I have a bunch of steps in this job I am running, and would like
to override the INCLUDE member being called by coding it instream in the
top of the job, just as you would do with an instream PROC. I don't want to
On Mon, 25 Mar 2013 15:41:52 -0500, Nguyen Dt wrote:
Tested the delete with IDCAMS NVR option, doesn't work .. do i miss something
?
...
IDC3009I ** VSAM CATALOG RETURN CODE IS 102 - REASON CODE IS IGG0CLFP-7
The data set was not deleted because it was open.
Did you even try to look up the
I haven't seen any syntax to do that. Why not use a instream PROC? You can
now nest a PROC within another PROC, so you could use an instream PROC much
like an instream INCLUDE.
//INSTREAM PROC
//STEP EXEC PGM=WANDA
//DD1
// PEND
// EXEC PROC=EXTPROC,IPROC=INSTREAM
//
//EXTPROC PROC IPROC=
//
It appears to be allowed, but it gets corrected and the data set deleted.
2 //GETNO EXEC PGM=ISFAFD
3 //ISFOUT DD DISP=(NEW,CATLG),
//SPACE=(TRK,(2,1)),RECFM=FB,LRECL=133,UNIT=SYSDA
4 //ISFINDD *
STMT NO.
I was planning to override an existing INCLUDE for a common set of STEPLIB
files, but for different programs. I was hoping I wouldn't have to make a
lot of changes to the JCL just for this simple test I am running.
Billy
On Mon, Mar 25, 2013 at 4:53 PM, John McKown
Ah. I get you, now. I might try using the JCLLIB statement so that my
personal JCL proclib was in front of the system proclibs. Then put a
member in my proclib with the same name as used in the system proc for the
INCLUDE member. Like putting your own macro/copy library in front of the
system
In this case, are you sure it is orphan? Not associated with some active job or
STC?
Dave Gibney
Information Technology Services
Washington State University
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
On Behalf Of Tom Marchant
Sent:
John,
What about //. SET
Scott ford
www.identityforge.com
Tell me and I'll forget; show me and I may remember; involve me and I'll
understand. - Chinese Proverb
On Mar 25, 2013, at 5:02 PM, John McKown john.archie.mck...@gmail.com wrote:
Ah. I get you, now. I might try using the
On Monday 25 March 2013 11:17:07 Bill Ashton wrote:
Hi guys...I have been asked to do some COBOL coding, and I have not done
some for quite a few years. Is there a COBOL listserv available, and is
there any other website that would have recommended best practices?
Try COBOL User
Anyone:
The sysut3 and sysut4 restriction from the fine manual I believe syas
there should be a specific allocation. IT seems reasonable to me that
indeed if there is a restriction it at the minimum should be
documented in the CURRENT manual and *IF* these are dynamically
allocated
On 25 March 2013 18:14, Ed Gould edgould1...@comcast.net wrote:
The sysut3 and sysut4 restriction from the fine manual I believe syas there
should be a specific allocation. IT seems reasonable to me that indeed if
there is a restriction it at the minimum should be documented in the CURRENT
On 25 March 2013 14:32, Robert A. Rosenberg hal9...@panix.com wrote:
At 12:49 -0500 on 03/25/2013, Ducky duke wrote about Dataset DELETE question
Tried with IDCAMS DELETE :
//STEP010 EXEC PGM=IDCAMS
//DD01 DD DSN=SYS12048.T104505.RA000.IBMUSER.R018,
//
On 25 Mar 2013 11:52:27 -0700, in bit.listserv.ibm-main you wrote:
On Mon, 25 Mar 2013 11:03:25 -0700, Ed Jaffe wrote:
I gotta ask. Why not just try this yourself? You no longer work for an ISV?
Trying it on 1.13 (which I am allowed to discuss) I get:
IEFC004I OPEN OF JCLLIB DATASETS WAS
At 12:22 -0700 on 03/25/2013, Ed Jaffe wrote about Re: More JES2:
looking ahead:
On 3/25/2013 12:18 PM, Ed Jaffe wrote:
The existence of ISV Early Programs is no secret:
http://dtsc.dfw.ibm.com/MVSDS/'HTTPD2.DSN01.PUBLIC.PDF(ISVEPROG)'
Note: Some browsers might not like the apostrophes in
At 18:40 + on 03/25/2013, Gibney, Dave wrote about Re: Dataset
DELETE question : IEBFR14 vs IDCAMS:
Actually, the missing NVR (NonVsam Record) as suggested by Allan
should have accomplished the task. It basically tells IDCAMS not to
fail if the Catalog record is missing.
Dave Gibney
At 14:00 -0500 on 03/25/2013, Paul Gilmartin wrote about Re: Dataset
DELETE question : IEBFR14 vs IDCAMS:
x-charset UTF-8On Mon, 25 Mar 2013 14:38:41 -0400, Steve Thompson wrote:
Now, go whack the person that wrote the JCL that has the following
similarly coded DD statement:
//SYSUT3 DD
SMPE (I believe) does not (last time I checked) and it does generate
a compress (if told to retry).
Ed
On Mar 25, 2013, at 7:02 PM, Tony Harminc wrote:
On 25 March 2013 18:14, Ed Gould edgould1...@comcast.net wrote:
The sysut3 and sysut4 restriction from the fine manual I believe
syas
On 3/25/2013 5:32 PM, Clark Morris wrote:
And I was delighted to discover that 1.13 supports instream data in
instream PROCs (JES2 only). Documented, with revision bars. We'll
need to see whether 2.1 removes (2) as a cause. I used RECFM=V,
LRECL=130.
Once again the cheaper Job Entry Subsystem
62 matches
Mail list logo
