> I would expect that the return codes should be standardized.
That is not the case with the CSI stack.
Tony Thigpen
Edward M. Martin wrote on 01/16/2017 09:19 AM:
> Hello Everyone,
>
> I have this from the z/OS manuals (sorry we were forced to switch) for
> return code 000008.
>
> I would expect that the return codes should be standardized.
>
> 8 EAI_SERVICE GETADDRINFO The SERVICE was not
>
> recognized for the
>
> specified socket type.
>
> Correct the SERVICE.
>
> 8 ENOEXEC All An
> EXEC format error
>
> occurred.
>
> Check that the target
>
> module on an exec call
>
> is a valid executable
>
> module.
>
> Edward M. Martin
>
> Aultman Health Foundation
>
> HealthQuest Team Member
>
> External
330-363-9666
>
> Internal 39666
>
> AultmanLogo
>
> *From:*VSE-L
> [mailto:
vse-l-bounces+edward.martin=
aultm...@lists.lehigh.edu] *On
> Behalf Of *Kevin Corkery
> *Sent:* Monday, January 16, 2017 8:34 AM
> *To:* 'VSE Discussion List'
> *Subject:* RE: TEL905W
>
> I guess it would be helpful if they documented the values in the reason
> code but I couldn’t find it anywhere. My best guess on this is a
> timeout event on an idle terminal (maybe one where the user just turned
> off the device) that wants to write something to the screen but the
> session is no longer available. If it’s something benign like that you
> can always have the message suppressed.
>
> *From:*VSE-L [mailto:
vse-l-bounces+kcorkery=
live...@lists.lehigh.edu]
> *On Behalf Of *Billy Bingham
> *Sent:* Monday, January 16, 2017 7:36 AM
> *To:* VSE Discussion List
> *Subject:* TEL905W
> *CONFIDENTIALITY NOTICE:* This e-mail (including the information it
> contains and attachments) is a business communication intended for the
> authorized use by the person who requested it, or for the authorized use
> by the intended recipient to perform an employment duty or business
> function. This e-mail may contain confidential, privileged, or
> proprietary information, including (but not limited to) Protected Health
> Information covered by the Health Insurance Portability and
> Accountability Act (HIPAA). It also may be protected by the Electronic
> Communications Act. If you received this e-mail by mistake, either
> directly or inadvertently as a recipient on a copied or forwarded
> e-mail, promptly notify us by return e-mail. Destroy this e-mail, the
> information, and attachments you received by mistake. You must not
> print, use, forward, or disclose to any third party by electronic,
> written or oral means any information you received by mistake. We do not
> waive any privilege. We may take legal steps or other appropriate
> action, as needed, to protect the confidentiality and privilege of any
> information inadvertently disclosed.