Hi All, In the past when STARMON didn’t get all data in time it abended, and the entire pipeline with it, with an RC=313. I have coded the REXX exec to restart the MONWRITE machine when that happens.
I now have the 313 error but the PIPELINE didn’t abend. In fact, the PIPE is still alive but STARMON doesn’t process any records after this event. Has this behavior changed in the newer PIPE version? I had been using the upstream runtime version in z/VM 5.4 and 6.3. Obviously in 6.4 and 7.1 I now use the IBM supplied version. FPLIUS313E IPRCODE Message was purged received on IUCV instruction. FPLMSG003I ... Issued from stage 1 of pipeline 5. FPLMSG001I ... Running "STARMON MONDCSS SHARED". FPLSMG313E IPRCODE 00000939 received on IUCV instruction. FPLMSG003I ... Issued from stage 1 of pipeline 5. FPLMSG001I ... Running "STARMON MONDCSS SHARED". What would be the best way to handle the abend? Is there a way to end the PIPE so that the REXX code can restart the PIPELINE? 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.
