ca.portal.admin

Re: Programming Question/ Bug?

Discussion created by ca.portal.admin on Aug 27, 2007
Petra,

I believe ADS does it best at converting the string (PIC X(14)) to a
number, by looking for any digits in the string and using those. It
would
of course have been much easier if CA had decided not to allow the
comparison in the first place.

I do not think the conversion used for the evaluation is actually
documented so you can expect that the behavior will change between
releases. The solution is to ensure that you tell ADS what you want.
In
this case I guess from the statement that you want to capture when only
zeroes were entered in the field. but not if it was left with spaces.

if p-invoice-no not = space and replacing(p-invoice-no,'0',' ') = space
do.
-
-
end.

Remember the only thing that sets 0 and space apart from other bit
combinations is the way they are interpreted by humans.

The last order of business is to subject the offending party (any
programmer comparing numeric and alphanumeric fields to each other) to
daily public beatings for a week. Then send them to an assembler class
as
a deterrent to others.


Tommy Petersen





Petra LaFrese
<lafresep@U.ARIZO
NA.EDU>
To
Sent by: IDMS IDMS-L@LISTSERV.IUASSN.COM
Public Discussion
cc
Forum
<IDMS-L@LISTSERV.
Subject
IUASSN.COM> Programming Question/ Bug?


08/21/2007 01:12
PM


Please respond to
IDMS Public
Discussion Forum
<IDMS-L@LISTSERV.
IUASSN.COM>







One of my programmers asked me this question. I am not sure why this
happens.

Field P-INVOICE-NO is defined as Pic X(14). Code in the ADS program
checks if the field contains zeros using any of the following lines of
code:

IF P-INVOICE-NO OF IAVMRPPV = 0
IF P-INVOICE-NO OF IAVMRPPV = ZEROS
IF P-INVOICE-NO OF IAVMRPPV = ZEROES

If the field is all zeroes, it executes an error message, as it
should. But if the field is changed to 0A (or any 0 and alpha combo)
and enter is pressed - the screen does not recognize that the field
now contains something other than 0, or zeros, or zeroes and still
produces the error message. This is happening in programs that are
recently changed. We are running IDMS V16.0 Service Pack 4.

I have searched Support Connect and have found no mention of such a
problem. Has anyone heard of or experienced this? How did you fix
it? The programmer got around this by checking for 0 in every
position of the field, but the code above is used in several of our
programs and has us concerned.

Thanks for your help.
Petra
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: [IDMSVENDOR-L] Calling IDMSCOM
"Hi all,
Just did some checking with CA to see if my recolection on spanned
records was correct.

It was.

Here's Carla's response to my question via Randy at CA tech support.

""Here's the response from Carla:

""Hi Randy - CULLJRNL does not recompose spanned records and it would be
very
difficult to alter it to do this. The segments of a spanned record are
not
necessarily written consecutively in the journal file. Any number of
records
can be written between the first segment and each of the remaining
segments.
The JREPORTs, which utilize CULLJRNL, are written to process each
journal
record as it is read sequentially in the file. It will print an
appropriate
title to indicate whethere this is an extension of a previous record or
the
first part of a spanned record. It does not attempt to recompose the
spanned record to report on it with one entry.""


Dick

Richard Pierce
(617) 973-8911
richard.pierce@state.ma.us

Outcomes