Robelle Technical Database Reference KB16063

Originator: PAUL GOBES  


why does stream * set cierror = 383?
email on Robelle-L:
> I have a batch job editing files and STREAMing jobs.  I wanted to check
> CIERROR=0 to determine whether to delete or 'save' the STDLIST.  The IF

> kept failing with 383.  I narrowed it down to STREAM * changes CIERROR to
> 383.  Everything else I was doing in QEDIT kept CIERROR at zero, if it was
> successful.
> 
> Why does QEDIT set CIERROR to 383 after STREAMing the workfile?
> 

> Is it safe to check CIERROR = 383 to allow for the deleting of the
> $stdlist?
> 
> Or what other system VARs can be checked to insure that a batch job doing
> only QEDIT commands and STREAMing jobs worked successfully?

------------------------------------------------------------------
As for the other 2 questions, I plan on answering that it safe to delete
the job on cierror=383, and I don't know of any other system VAR to check.

But I couldn't find any answer for the first question about why stream*
sets the cierror jcw.
n.b.  a simple /stream myjob  does not set this cierror jcw.
/paul


Append: (O:O) HANS HENDRIKS  Checks for temporary file     04 Jul00 12:05 PM 
KB 15573 shows that when you do a "stream *", Qedit saves the current file
into a temporary file called "qeditjob". Cierror is set to 383 when you try

to purge a nonexistent file. My guess is that Qedit tries to purge
qeditjob,temp before saving the current file to that name, and fails.
Verified by first building a qeditjob temp file, so the purge doesn't fail:
/build qeditjob,temp
/stream *

 #J4728
/showjcw cierror
CIERROR = 0


Append: (O:E) FRANCOIS DESROCChange status                 23 Aug00 12:36 PM 
After 5.0 is released, I'll check this and see if we can safely reset the
JCW.

Comment on this KB entry

Your comments will be sent to Robelle technical support. Any updates will be reflected on the website the following day.

• Log a new bug report
• Log a new enhancement request