Use DISKSLOW if you know you are going to write a single line per
invocation.
The reason could be anything; Vblockv is totally undocumented. Use >SFS
to get documented error and reason codes.
I don't know what your PUTFILES does, so I cannot answer your final
question.
On 3/3/21 12:43, van Sleeuwen, Berry wrote:
Hi All,
I have a REXX with a number of PUTFILES stages. Each of them will save a report
in a group of files. The REXX is executed every minute.
Two times today I got an FPL120E in one of the PUTFILES stages. It looks like
the error only appears in the GSTVM000 files, or at least the other PUTFILES
stages didn’t have an error (yet).
FPLDSR120E Return code 16 from parameter list Vblockw GSTVM000 TCPIP A1
FPLMSG003I ... Issued from stage 2 of pipeline 2
FPLMSG001I ... Running "> GSTVM000 TCPIP A"
FPLDSR120E Return code 16 from parameter list Vblockw GSTVM000 HIDRO A1
FPLMSG003I ... Issued from stage 2 of pipeline 2
FPLMSG001I ... Running "> GSTVM000 HIDRO A"
<Repeated 6 times for each file in the stage>
According to the docs a return code 16 suggests that PUTFILES attempts to write
to the same file. But as far as I can find there shouldn’t be a duplicate file.
The input for this stage actually contains just one line for each file so
PUTFILES only needs to write 1 record to each file in each execution run.
Last night I ran the code with traces for a couple of hours, and obviously
Murphy made sure there was no error during that time.
What could be the reason for this error? Is there another reason other than the
“duplicate file” in this case?
And generally, I run a number of PUTFILES stages in the REXX for each report.
Is that accepted or should I redirect all data to one single PUTFILES stage?
Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen,
Berry van Sleeuwen
Flight Forum 3000 5657 EW Eindhoven
This e-mail and the documents attached are confidential and intended solely for
the addressee; it may also be privileged. If you receive this e-mail in error,
please notify the sender immediately and destroy it. As its integrity cannot be
secured on the Internet, Atos’ liability cannot be triggered for the message
content. Although the sender endeavours to maintain a computer virus-free
network, the sender does not warrant that this transmission is virus-free and
will not be liable for any damages resulting from any virus transmitted. On all
offers and agreements under which Atos Nederland B.V. supplies goods and/or
services of whatever nature, the Terms of Delivery from Atos Nederland B.V.
exclusively apply. The Terms of Delivery shall be promptly submitted to you on
your request.
