IDCAMS REPRO vs SYSB-II question

[McKown, John]

We had a very strange occurrance last night. We ran an IDCAMS step which
did a REPRO from a sequential file to a VSAM file which was being
accessed via SYSB-II. The IDCAMS output was:

IDCAMS SYSTEM SERVICES TIME:
21:28:45 12/28/04 PAGE 1

REPRO INFILE(IFILE01) OUTFILE(OFILE01) REPLACE
00010000
IDC0005I NUMBER OF RECORDS PROCESSED WAS 23743
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8

IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 8

The JESLOG for the step was:

*-PPRI014D JS010 PS020 00 123 .01 .00 .1 7642
0 0 0 0 0
SYSB352 DDNAME OFILE01 SUBSYS PARAMETERS TAKEN FROM
GLOBAL ENTRY
-- SYNC=10000
SUBSYS= PARAMETERS
-- CICS=P3CH
-- TERMS=SYSB001-50
-- NOCICSOK
-- SYNC=500
SYSB-II - THE BATCH CONNECTION TO CICS VERSION 5.0.0FP13 (C)
1991-2000 H&W COMPUTER SYSTEMS, INC.
SYSB004 ATTEMPTING CONNECT TO P3CH USING SUBSYSTEM SYSB
SYSB005 SUCCESSFULLY CONNECTED TO P3CH (0530X 05.0.0 P13) USING
SYSB001
SYSB008 COMMUNICATION TO P3CH IS WITH HPO (VTAM REL 614)
SYSB367 OFILE01 OPEN FOR OUTPUT TO FCT=GCR05KSD,
DSN=PRIPV.PR.GCR05KSD.DATA
***************************************** SYSB-II FILE STATISTICS
******************************************
DD-NAME --SEQ-GET --DIR-GET SEQ-GET-U DIR-GET-U --SEQ-PUT --DIR-PUT
SEQ-PUT-U DIR-PUT-U ----POINT ----ERASE
OFILE01 0 0 2,007 0 23,746 0
2,007 0 0 0
FCTNAME -----READ ----WRITE --REWRITE ---DELETE ---UNLOCK --STARTBR
-READNEXT -READPREV --RESETBR ----ENDBR
GCR05KSD 2,010 23,746 2,007 0 3 0
0 0 0 0
NUMBER OF SYNCPOINTS TRIGGERED = 56
*-PPRI014D JS010 PS025 ,08, 1120 .03 .00 4.5 14739
0 0 0 0 0

There are no messages of any kind as to why IDCAMS got the RC=8. In
addition, the REPRO record count was three(3) less than the size of the
input file (as recorded in a previous SORT step).

We have contacted H&W about this as well, but I thought it weird that
IDCAMS would terminate with an RC=8 and no error message.

--
John McKown
Senior Systems Programmer
UICI Insurance Center
Information Technology

This message (including any attachments) contains confidential
information intended for a specific individual and purpose, and its'
content is protected by law. If you are not the intended recipient, you
should delete this message and are hereby notified that any disclosure,
copying, or distribution of this transmission, or taking any action
based on it, is strictly prohibited.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

[Brian Peterson]

I know nothing about SYSB-II, but the below looked odd.... You're not
trying to REPRO directly into the data component of a VSAM KSDS, are you?

Brian

On Wed, 29 Dec 2004 15:19:05 -0600, McKown, John

Post by McKown, John
SYSB367 OFILE01 OPEN FOR OUTPUT TO FCT=GCR05KSD,
DSN=PRIPV.PR.GCR05KSD.DATA

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

[McKown, John]

-----Original Message-----
From: IBM Mainframe Discussion List
Sent: Wednesday, December 29, 2004 3:23 PM
Subject: Re: IDCAMS REPRO vs SYSB-II question
I know nothing about SYSB-II, but the below looked odd.... You're not
trying to REPRO directly into the data component of a VSAM
KSDS, are you?
Brian
On Wed, 29 Dec 2004 15:19:05 -0600, McKown, John

Post by McKown, John
SYSB367 OFILE01 OPEN FOR OUTPUT TO FCT=GCR05KSD,
DSN=PRIPV.PR.GCR05KSD.DATA

I thought it odd too, but the DSN= on that message appears to be
incorrect. The FCT in CICS does not have the .DATA on it. Neither does
the DSN= in the JCL.

--
John McKown
Senior Systems Programmer
UICI Insurance Center
Information Technology

This message (including any attachments) contains confidential
information intended for a specific individual and purpose, and its'
content is protected by law. If you are not the intended recipient, you
should delete this message and are hereby notified that any disclosure,
copying, or distribution of this transmission, or taking any action
based on it, is strictly prohibited.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

[Peter Vander Woude]

John,

Were there any messages in the CICS stc output relating to the file?
Might there have been a problem extending the vsam file?



Peter I. Vander Woude

Sr. Mainframe Engineer
Harris Teeter, Inc.
We had a very strange occurrance last night. We ran an IDCAMS step
which
did a REPRO from a sequential file to a VSAM file which was being
accessed via SYSB-II. The IDCAMS output was:

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

[McKown, John]

-----Original Message-----
From: IBM Mainframe Discussion List
Sent: Wednesday, December 29, 2004 3:37 PM
Subject: Re: IDCAMS REPRO vs SYSB-II question
John,
Were there any messages in the CICS stc output relating to the file?
Might there have been a problem extending the vsam file?
Peter I. Vander Woude
Sr. Mainframe Engineer
Harris Teeter, Inc.

No CICS messages in the region involved. No SYSB messages in the region
involved. No messages in SYSLOG. No messages anywhere that we can find.
Very confusing!

--
John McKown
Senior Systems Programmer
UICI Insurance Center
Information Technology

This message (including any attachments) contains confidential
information intended for a specific individual and purpose, and its'
content is protected by law. If you are not the intended recipient, you
should delete this message and are hereby notified that any disclosure,
copying, or distribution of this transmission, or taking any action
based on it, is strictly prohibited.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

[Peter Hunkeler]

On Wednesday, 29.12.2004 at 15:19 CST, "McKown, John"

Post by McKown, John
IDC0005I NUMBER OF RECORDS PROCESSED WAS 23743
***************************************** SYSB-II FILE STATISTICS
******************************************
DD-NAME --SEQ-GET --DIR-GET SEQ-GET-U DIR-GET-U --SEQ-PUT --DIR-PUT
SEQ-PUT-U DIR-PUT-U ----POINT ----ERASE
OFILE01 0 0 2,007 0 23,746 0
2,007 0 0 0
FCTNAME -----READ ----WRITE --REWRITE ---DELETE ---UNLOCK --STARTBR
-READNEXT -READPREV --RESETBR ----ENDBR
GCR05KSD 2,010 23,746 2,007 0 3 0

Not that this is really helpful but I find it interesting that the SYSB-II
file statistics says it has SEQ-PUT 23746 records, which seems to be the
number you'd expect (IDCAMS count + 3). Same number appears under WRITE.

Peter Hunkeler
Senior IT Specialist, IBM zSeries Technical Sales Support, Switzerland

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html