Unidata's Idle State Question 
Author Message
 Unidata's Idle State Question

Here's a problem we just had on Unidata 3.1.5b:

I am running through a process that loads data onto a PC from the Pick
environment. If I encounter an invalid piece of data I fill an error array, to
be printed out at the end of the process. The problem occurs when this
particular piece of data is too long (its 35 chars instead of 25). I try to
tell the user the problem by placing the offending data in an error message (I
really, really, really hate messages like : Somwhere near line ...). Here is
the line of code I use:

111      ERR.MSG = "Data item :"BLD.ITM:" is larger than the assigned field
size of ":FLD.SZ:"."

BLD.ITM is the offending data.
FLD.SZ is the field size variable.

For some reason we hit this line and go into that never never land of the idle
state. Debugs directly after line 111 never happen.

To top it off, Unidata reps claim its not one of their Bugs. They
claim it must be our product's bug. Just a tad irritating.

Anyone else run into this? Your input has been, and I'm sure will be greatly
appreciated.

--
Michael Prodor                    "Prepare your Heinie for my Spank Ray"



Tue, 25 Aug 1998 03:00:00 GMT
 
 [ 1 post ] 

 Relevant Pages 

1. Another 'State and County tables' question

2. Pick/Unidata Contractors needed for Washington State-U.S.-(Recruiter)

3. sql state '28000' error 188456

4. Can't find an idle worker thread for XaStart

5. ODBC Connection Fail, SQL State: '01000'

6. Connection failed: SQL State 'S1000' - HELP

7. Connecting Problem / SQL State '08001'

8. how to close idle connection created with php's pg_pconnect()

9. JZ0R1...result set is IDLE...but shouldn't be

10. jim idle, this bud's for you !

11. Unidata/Unix Processes 'fading'

12. Unidata 'udstat' verb


 
Powered by phpBB® Forum Software