DB2 v7 OS/390 & QMF v7.2

Steve Whittaker

DB2 v7 OS/390 & QMF v7.2
Wonder if anyone can help me with this.
We have a production job that runs once a year and last ran Jan. 2003 with no problems. Since then we have migrated to DB2 v7 OS/390. The job went to run this past week and failed. The batch job calls a proc and here's a sample of what the proc is doing:

/* REXX EXEC */

DT=DATE(U);
TM=TIME();
OUTLN.1 = 'SMCREADO.RMCQ25_P ' || DT || ' ' || TM
OUTLN.0 = 1

"RUN QUERY SMCREADO.RMCQSET_Q"
SRC = RC
IF SRC <> 0 THEN DO
OUTLN.1 = OUTLN.1 || ' RUN QUERY SMCREADO.RMCQSET_Q '
ADDRESS TSO 'EXECIO ' OUTLN.0 ' DISKW ' OUTF '(FINIS STEM OUTLN.'
EXIT
END

And here is what error msg they say came out from the Production job that was submitted:

VIEW 2.0 BROWSE - JBMCQRYA-UTL - REC 0000000 PG 0000001.001 LOCK 00 COL 001 080
COMMAND ===> SCROLL ===> CSR
********************************* TOP OF DATA **********************************
.SARPAGE 1
.IKJ56644I NO VALID TSO USERID, DEFAULT USER ATTRIBUTES USED
.READY
. ISPSTART PGM(DSQQMFE) NEWAPPL PARM(S=PR10,I=SMCREADO.RMCQ25_P,M=B)
.IRX0555E The input or output file OUTF is not allocated. It cannot be opened fo
.IRX0670E EXECIO error while trying to GET or PUT a record.
.READY
.END
******************************** BOTTOM OF DATA ********************************

Anyone have any ideas of what might have happened. Unfortunately for me the original outlist is long gone and they just involved the DBA's after the fact.
Appreciate any insight.

Thanks:
--STeve....


Raleigh, NC
email: [login to unmask email]
Ph: 919-546-7267

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

David Seibert

Re: DB2 v7 OS/390 & QMF v7.2
(in response to Steve Whittaker)
Hi Steve,

The Rexx error message on Execio leads me to suspect that there's a
problem with the allocation of the DDname OUTF.

Can you review the JCL or the rest of the Rexx program to ensure that a file
is being allocated to the OUTF DDname, in JCL with a DD statement or in the
Rexx code with an "alloc F(outf) dsn(....)...." statement?

Can you recreate the problem?

Dave


-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email]On
Behalf Of Whittaker, Stephen
Sent: Friday, January 16, 2004 1:28 PM
To: [login to unmask email]
Subject: DB2 v7 OS/390 & QMF v7.2


Wonder if anyone can help me with this.
We have a production job that runs once a year and last ran Jan. 2003 with
no problems. Since then we have migrated to DB2 v7 OS/390. The job went to
run this past week and failed. The batch job calls a proc and here's a
sample of what the proc is doing:

/* REXX EXEC */

DT=DATE(U);
TM=TIME();
OUTLN.1 = 'SMCREADO.RMCQ25_P ' || DT || ' ' || TM
OUTLN.0 = 1

"RUN QUERY SMCREADO.RMCQSET_Q"
SRC = RC
IF SRC <> 0 THEN DO
OUTLN.1 = OUTLN.1 || ' RUN QUERY
SMCREADO.RMCQSET_Q '
ADDRESS TSO 'EXECIO ' OUTLN.0 ' DISKW ' OUTF
'(FINIS STEM OUTLN.'
EXIT
END

And here is what error msg they say came out from the
Production job that was submitted:

VIEW 2.0 BROWSE - JBMCQRYA-UTL - REC 0000000
PG 0000001.001 LOCK 00 COL 001 080
COMMAND ===>
SCROLL ===> CSR
********************************* TOP OF
DATA **********************************
.SARPAGE 1
.IKJ56644I NO VALID TSO USERID, DEFAULT USER
ATTRIBUTES USED
.READY
. ISPSTART PGM(DSQQMFE) NEWAPPL
PARM(S=PR10,I=SMCREADO.RMCQ25_P,M=B)
.IRX0555E The input or output file OUTF is
not allocated. It cannot be opened fo
.IRX0670E EXECIO error while trying to GET
or PUT a record.
.READY
.END
******************************** BOTTOM OF
DATA ********************************

Anyone have any ideas of what might have happened.
Unfortunately for me the original outlist is long gone and they just
involved the DBA's after the fact.
Appreciate any insight.

Thanks:
--STeve....


Raleigh, NC
email: [login to unmask email]
Ph: 919-546-7267




The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Steve Whittaker

Re: DB2 v7 OS/390 & QMF v7.2
(in response to David Seibert)
Dave:
I will look at the JCL and see what I can find. In the actual PROC itself there is no allocation being done at all. Looks like the Production JCL calls some procs and members so it may be in there..
Thanks for the tip and I'll let you know what I find out. As for recreating it; I'll have to ask the client since I'm not sure what all this batch job is doing.

--Steve....

-----Original Message-----
From: Seibert, Dave [mailto:[login to unmask email]
Sent: Friday, January 16, 2004 1:39 PM
To: [login to unmask email]
Subject: Re: DB2 v7 OS/390 & QMF v7.2


Hi Steve,

The Rexx error message on Execio leads me to suspect that there's a
problem with the allocation of the DDname OUTF.

Can you review the JCL or the rest of the Rexx program to ensure that a file
is being allocated to the OUTF DDname, in JCL with a DD statement or in the
Rexx code with an "alloc F(outf) dsn(....)...." statement?

Can you recreate the problem?

Dave


-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email]On
Behalf Of Whittaker, Stephen
Sent: Friday, January 16, 2004 1:28 PM
To: [login to unmask email]
Subject: DB2 v7 OS/390 & QMF v7.2


Wonder if anyone can help me with this.
We have a production job that runs once a year and last ran Jan. 2003 with
no problems. Since then we have migrated to DB2 v7 OS/390. The job went to
run this past week and failed. The batch job calls a proc and here's a
sample of what the proc is doing:

/* REXX EXEC */

DT=DATE(U);
TM=TIME();
OUTLN.1 = 'SMCREADO.RMCQ25_P ' || DT || ' ' || TM
OUTLN.0 = 1

"RUN QUERY SMCREADO.RMCQSET_Q"
SRC = RC
IF SRC <> 0 THEN DO
OUTLN.1 = OUTLN.1 || ' RUN QUERY
SMCREADO.RMCQSET_Q '
ADDRESS TSO 'EXECIO ' OUTLN.0 ' DISKW ' OUTF
'(FINIS STEM OUTLN.'
EXIT
END

And here is what error msg they say came out from the
Production job that was submitted:

VIEW 2.0 BROWSE - JBMCQRYA-UTL - REC 0000000
PG 0000001.001 LOCK 00 COL 001 080
COMMAND ===>
SCROLL ===> CSR
********************************* TOP OF
DATA **********************************
.SARPAGE 1
.IKJ56644I NO VALID TSO USERID, DEFAULT USER
ATTRIBUTES USED
.READY
. ISPSTART PGM(DSQQMFE) NEWAPPL
PARM(S=PR10,I=SMCREADO.RMCQ25_P,M=B)
.IRX0555E The input or output file OUTF is
not allocated. It cannot be opened fo
.IRX0670E EXECIO error while trying to GET
or PUT a record.
.READY
.END
******************************** BOTTOM OF
DATA ********************************

Anyone have any ideas of what might have happened.
Unfortunately for me the original outlist is long gone and they just
involved the DBA's after the fact.
Appreciate any insight.

Thanks:
--STeve....


Raleigh, NC
email: [login to unmask email]
Ph: 919-546-7267




The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Tony Provenzola

Re: DB2 v7 OS/390 & QMF v7.2
(in response to Steve Whittaker)
"ADDRESS TSO 'EXECIO ' OUTLN.0 ' DISKW ' OUTF '(FINIS STEM OUTLN.'"
"IRX0555E The input or output file OUTF is not allocated."

I can't tell you what changed (why it used to work), but I can tell you what's wrong now. It's attempting to write the output to DDNAME OUTF, and that DDNAME doesn't exist. Either the output DD hasn't been allocated (with an ALLOC statement in the REXX or a DD Card in your JCL) or it has been allocated with another DDNAME and the DDNAME hasn't been moved to the variable OUTF. If no value is moved to a variable, the default value is the name of the variable.

- If OUTF is the DDNAME you want, make sure that it exists prior to the EXECIO statement.
- If the intent is to write to another DDNAME that does exist, move the DDNAME to the variable OUTF.

Tony Provenzola
Nike Database Services
Venturi Technology Partners, Consulting
Phone * 503-532-0772
Fax * 503-532-3223
Email * [login to unmask email]


-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email]On
Behalf Of Whittaker, Stephen
Sent: Friday, January 16, 2004 10:28 AM
To: [login to unmask email]
Subject: DB2 v7 OS/390 & QMF v7.2


Wonder if anyone can help me with this.
We have a production job that runs once a year and last ran Jan. 2003 with no problems. Since then we have migrated to DB2 v7 OS/390. The job went to run this past week and failed. The batch job calls a proc and here's a sample of what the proc is doing:

/* REXX EXEC */

DT=DATE(U);
TM=TIME();
OUTLN.1 = 'SMCREADO.RMCQ25_P ' || DT || ' ' || TM
OUTLN.0 = 1

"RUN QUERY SMCREADO.RMCQSET_Q"
SRC = RC
IF SRC <> 0 THEN DO
OUTLN.1 = OUTLN.1 || ' RUN QUERY SMCREADO.RMCQSET_Q '
ADDRESS TSO 'EXECIO ' OUTLN.0 ' DISKW ' OUTF '(FINIS STEM OUTLN.'
EXIT
END

And here is what error msg they say came out from the Production job that was submitted:

VIEW 2.0 BROWSE - JBMCQRYA-UTL - REC 0000000 PG 0000001.001 LOCK 00 COL 001 080
COMMAND ===> SCROLL ===> CSR
********************************* TOP OF DATA **********************************
.SARPAGE 1
.IKJ56644I NO VALID TSO USERID, DEFAULT USER ATTRIBUTES USED
.READY
. ISPSTART PGM(DSQQMFE) NEWAPPL PARM(S=PR10,I=SMCREADO.RMCQ25_P,M=B)
.IRX0555E The input or output file OUTF is not allocated. It cannot be opened fo
.IRX0670E EXECIO error while trying to GET or PUT a record.
.READY
.END
******************************** BOTTOM OF DATA ********************************

Anyone have any ideas of what might have happened. Unfortunately for me the original outlist is long gone and they just involved the DBA's after the fact.
Appreciate any insight.

Thanks:
--STeve....


Raleigh, NC
email: [login to unmask email]
Ph: 919-546-7267

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Steve Whittaker

Re: DB2 v7 OS/390 & QMF v7.2
(in response to Tony Provenzola)
Thanks to all.
Here's what I've found on the OUTF dataset. In the PROC that is called by the Production job the OUTF stmt is 'commented out'. BUT the dataset that was commented out still exists. When I went to bring it up in 3.4 it was migrated. So it took about 5+ minutes to come back. And it did contain 3 very old rows in there.
I'm wondering if since OUTF dataset was migrated if this might have caused the failure. Maybe it wouldn't wait that long?? But it cleary states that it was not allocated.
I'm going to ask the client if they can rerun the job and this time DON'T delete the outlist so I can look at it. :-)
Appreciate the reponses..


--Steve....

-----Original Message-----
From: Provenzola, Tony [mailto:[login to unmask email]
Sent: Friday, January 16, 2004 1:49 PM
To: [login to unmask email]
Subject: Re: DB2 v7 OS/390 & QMF v7.2


"ADDRESS TSO 'EXECIO ' OUTLN.0 ' DISKW ' OUTF '(FINIS STEM OUTLN.'"
"IRX0555E The input or output file OUTF is not allocated."

I can't tell you what changed (why it used to work), but I can tell you what's wrong now. It's attempting to write the output to DDNAME OUTF, and that DDNAME doesn't exist. Either the output DD hasn't been allocated (with an ALLOC statement in the REXX or a DD Card in your JCL) or it has been allocated with another DDNAME and the DDNAME hasn't been moved to the variable OUTF. If no value is moved to a variable, the default value is the name of the variable.

- If OUTF is the DDNAME you want, make sure that it exists prior to the EXECIO statement.
- If the intent is to write to another DDNAME that does exist, move the DDNAME to the variable OUTF.

Tony Provenzola
Nike Database Services
Venturi Technology Partners, Consulting
Phone * 503-532-0772
Fax * 503-532-3223
Email * [login to unmask email]


-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email]On
Behalf Of Whittaker, Stephen
Sent: Friday, January 16, 2004 10:28 AM
To: [login to unmask email]
Subject: DB2 v7 OS/390 & QMF v7.2


Wonder if anyone can help me with this.
We have a production job that runs once a year and last ran Jan. 2003 with no problems. Since then we have migrated to DB2 v7 OS/390. The job went to run this past week and failed. The batch job calls a proc and here's a sample of what the proc is doing:

/* REXX EXEC */

DT=DATE(U);
TM=TIME();
OUTLN.1 = 'SMCREADO.RMCQ25_P ' || DT || ' ' || TM
OUTLN.0 = 1

"RUN QUERY SMCREADO.RMCQSET_Q"
SRC = RC
IF SRC <> 0 THEN DO
OUTLN.1 = OUTLN.1 || ' RUN QUERY SMCREADO.RMCQSET_Q '
ADDRESS TSO 'EXECIO ' OUTLN.0 ' DISKW ' OUTF '(FINIS STEM OUTLN.'
EXIT
END

And here is what error msg they say came out from the Production job that was submitted:

VIEW 2.0 BROWSE - JBMCQRYA-UTL - REC 0000000 PG 0000001.001 LOCK 00 COL 001 080
COMMAND ===> SCROLL ===> CSR
********************************* TOP OF DATA **********************************
.SARPAGE 1
.IKJ56644I NO VALID TSO USERID, DEFAULT USER ATTRIBUTES USED
.READY
. ISPSTART PGM(DSQQMFE) NEWAPPL PARM(S=PR10,I=SMCREADO.RMCQ25_P,M=B)
.IRX0555E The input or output file OUTF is not allocated. It cannot be opened fo
.IRX0670E EXECIO error while trying to GET or PUT a record.
.READY
.END
******************************** BOTTOM OF DATA ********************************

Anyone have any ideas of what might have happened. Unfortunately for me the original outlist is long gone and they just involved the DBA's after the fact.
Appreciate any insight.

Thanks:
--STeve....


Raleigh, NC
email: [login to unmask email]
Ph: 919-546-7267

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm