× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. COBOL400-L
  3. November 2013

Re: *ISO date in COBOL?


It's stopping before it ever reads a record:

START EVENTS-IN KEY > EXTERNALLY-DESCRIBED-KEY
INVALID KEY
GO TO COPY-END.

Error:
Message ID . . . . . . : LNR7057

Date sent . . . . . . : 11/29/13 Time sent . . . . . . : 17:29:02



Message . . . . : I/O operation failed in program 'CCEXTRACT' in library

'IDOCKETGY'.



Cause . . . . . : Program 'CCEXTRACT' in library 'IDOCKETGY' issued an I/O

operation on file 'EVENTS' at COBOL statement '665 ' which failed with
file
status '90'; and no error handler existed. When an unsuccessful file
status
is received from an I/O operation, an AT END/INVALID KEY, USE PROCEDURE,
or
FILE STATUS should be coded to handle the error. Message issued at
statement
'665 ' of COBOL program 'CCEXTRACT' in program object 'CCEXTRACT' in
library
'IDOCKETGY'.


The program dump shows this for the BEGIN-DATE field:
BEGIN-DATE OF JE027006 OF MCEVNT-RECORD OF EVENTS-IN
CHAR(10) " "
"40404040404040404040"X

Which is expected, since nothings begin read into the field as yet.

TomH

-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx
[mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of
MichaelQuigley@xxxxxxxxxx
Sent: Friday, November 29, 2013 4:05 PM
To: cobol400-l@xxxxxxxxxxxx
Subject: Re: [COBOL400-L] *ISO date in COBOL?

I've received a lot of CPF5035 due to error code 17--well, I've dealt with
enough of them. It's always been that the value in the date is not valid.
Are you receiving the error on a READ or something else? I would debug the
program and see where the error is actually being signalled. Better yet,
find out the value of BEGIN-DATE just prior to the execution of the
statement where the CPF5035 is hit. Even if you're not going to do anything
with the date field, you have to have a valid value in it. In your case,
'0001-01-01' would be valid.

By the way, LOW-VALUE or LOW-VALUES is not acceptable. I would love to see
the compiler modified to move the lowest valid value to the field with
LOW-VALUE, but it doesn't. It moves in the lowest acceptable value for the
current collating sequence.

cobol400-l-bounces@xxxxxxxxxxxx wrote on 11/29/2013 01:00:03 PM:

From: cobol400-l-request@xxxxxxxxxxxx
To: cobol400-l@xxxxxxxxxxxx
Date: 11/29/2013 01:03 PM
Subject: COBOL400-L Digest, Vol 11, Issue 46 Sent by:
cobol400-l-bounces@xxxxxxxxxxxx

Send COBOL400-L mailing list submissions to
cobol400-l@xxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.midrange.com/mailman/listinfo/cobol400-l
or, via email, send a message with subject or body 'help' to
cobol400-l-request@xxxxxxxxxxxx

You can reach the person managing the list at
cobol400-l-owner@xxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of COBOL400-L digest..."
Today's Topics:

1. Re: *ISO date in COBOL? (Tom Hightower)

----- Message from "Tom Hightower" <tomh@xxxxxxxxxxx> on Fri, 29 Nov
2013 10:06:05 -0600 -----

To:

"'COBOL Programming on the IBM i \(AS/400 and iSeries\)'" <cobol400-
l@xxxxxxxxxxxx>

Subject:

Re: [COBOL400-L] *ISO date in COBOL?

A little more info:
Portion of calling CL:
/* OVERRIDE INPUT FILES */
OVRDBF FILE(EVENTS) TOFILE(JE027006)


DSPFFD for the date field in Je027006:
BEGIN_DATE DATE 10 10 39 Both
Field text . . . . . . . . . . . . . . . : Begin Date field
CCYY-MM-DD
Date Format . . . . . . . . . . . . . . . : *ISO
Coded Character Set Identifier . . . . . : 37


JE027006 is logical for physical file JE027000 The date field in
record number 4294967295 is: 2013-05-20


The error message:


Message ID . . . . . . : CPF5035

Date sent . . . . . . : 11/29/13 Time sent . . . . . . :
09:37:05



Message . . . . : Data mapping error on member JE027000


Cause . . . . . : A data mapping error occurred on field BEGIN_DATE in

record number 4294967295, record format JE027000, member number 1,
in member
JE027000 file JE027000 in library GYJEMS60CC, because of error code
17.
The
error code meanings follow:


17 -- The format of the data in a date, time, or timestamp field is
not
valid.


The SELECT statement (the calling CL does an override for this):
* INPUT EVENTS FILE
SELECT EVENTS-IN ASSIGN TO DATABASE-EVENTS
ORGANIZATION IS INDEXED
ACCESS IS DYNAMIC
RECORD KEY IS EXTERNALLY-DESCRIBED-KEY
WITH DUPLICATES.

The FD for it:
FD EVENTS-IN.
01 MCEVNT-RECORD. COPY DDSR-JE027006 OF EVENTS.


This is the compile statement being used:
/* OVERRIDE INPUT FILES */
OVRDBF FILE(EVENTS) TOFILE(JE027006)
/* COMPILE EXTRACTION PROGRAM FOR COUNTY CLERK */
CRTBNDCBL PGM(IDOCKETGY/CCEXTRACT) +
SRCFILE(IDOCKETGY/QCBLSRC) SRCMBR(*PGM) +
OPTION(*SOURCE) CVTOPT(*DATETIME *DATE) +
DBGVIEW(*ALL)



Thanks for any insight for this,
TomH


-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx
[mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
Sent: Wednesday, November 27, 2013 5:59 PM
To: COBOL Programming on the IBM i (AS/400 and iSeries)
Subject: Re: [COBOL400-L] *ISO date in COBOL?

Need to see more of the code then Tom - the SELECT clause and FD etc.
as
a
minimum.

Also what error code are you actually seeing?


On 2013-11-27, at 6:55 PM, Tom Hightower <tomh@xxxxxxxxxxx> wrote:

The programmer working on it says that she's doing the compile like
so:

CRTBNDCBL PGM(IDOCKETGY/CCEXTRACT) +
SRCFILE(IDOCKETGY/QCBLSRC) SRCMBR(*PGM) +
OPTION(*SOURCE) CVTOPT(*DATETIME *DATE) +
DBGVIEW(*ALL)

TomH



-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx
[mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
Sent: Wednesday, November 27, 2013 5:07 PM
To: COBOL Programming on the IBM i (AS/400 and iSeries)
Subject: Re: [COBOL400-L] *ISO date in COBOL?

Are you specifying CVTOPT(*DATE) on the compile? That will allow
dates

to come into the program correctly.


On 2013-11-27, at 5:54 PM, "Tom Hightower" <tomh@xxxxxxxxxxx> wrote:

Hi all. I've had a request to debug this issue and am having a bit
of a time at it. Here's my issue:

Sample PF TestPF:
BOA, char, 20 byes
FYA, char, 5 bytes
NBR, packed, 7.0
DATE, date, 10 (*ISO)

Sample LF TestLF
Key fields:
BOA
DATE

Many records have DATE field values of '0001-01-01' (I assume
that's
*loval)

The COBOL program is trying to use LF, but is getting a key mapping
error on the logical. How do I get past that key mapping error in
the program? I'm happy to supply any more info as needed.

TomH

--
This is the COBOL Programming on the IBM i (AS/400 and iSeries)
(COBOL400-L) mailing list To post a message email:
COBOL400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please
take

a moment to review the archives at
http://archive.midrange.com/cobol400-l.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com




--
This is the COBOL Programming on the IBM i (AS/400 and iSeries)
(COBOL400-L) mailing list To post a message email:
COBOL400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
http://archive.midrange.com/cobol400-l.

--
This is the COBOL Programming on the IBM i (AS/400 and iSeries)
(COBOL400-L) mailing list To post a message email:
COBOL400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
http://archive.midrange.com/cobol400-l.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com




--
This is the COBOL Programming on the IBM i (AS/400 and iSeries)
(COBOL400-L)
mailing list To post a message email: COBOL400-L@xxxxxxxxxxxx To
subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at http://archive.midrange.com/cobol400-l.


--
This is the COBOL Programming on the IBM i (AS/400 and iSeries)
(COBOL400-L) digest list
To post a message email: COBOL400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/cobol400-l.

--
This is the COBOL Programming on the IBM i (AS/400 and iSeries) (COBOL400-L)
mailing list To post a message email: COBOL400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/cobol400-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.