Message NONAME-W-NOMSG - VMS

This is a discussion on Message NONAME-W-NOMSG - VMS ; Hi everybody, I want to know about this message or this means a failure? I'd search on google but these answers werent enough ------------------------------------------------------------------------------------------ Job CARGA_TBACK_JDA_CT (queue SYS$NODE, entry 58) terminated with error status %NONAME-W-NOMSG, Message number 00000000 Server1::Prompt> Job ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Message NONAME-W-NOMSG

  1. Message NONAME-W-NOMSG

    Hi everybody, I want to know about this message or this means a
    failure? I'd search on google but these answers werent enough

    ------------------------------------------------------------------------------------------
    Job CARGA_TBACK_JDA_CT (queue SYS$NODE, entry 58) terminated with
    error status

    %NONAME-W-NOMSG, Message number 00000000

    Server1::Prompt>

    Job CARGA_TBACK_JDA_CT (queue SYS$NODE, entry 59) terminated with
    error status
    %NONAME-W-NOMSG, Message number 00000000

    Server1::Prompt>
    ------------------------------------------------------------------------------------------

    These jobs are running with submit command on a queue when these are
    finished show these messages:
    This node is running under OpenVMS v.7.3-2 with tcpip v.5.4

    I hope you opinions
    thanks.

    Eduardo


  2. Re: Message NONAME-W-NOMSG

    On Thu, 19 Jul 2007, lalo wrote:

    > Hi everybody, I want to know about this message or this means a
    > failure? I'd search on google but these answers werent enough
    >
    > ------------------------------------------------------------------------------------------
    > Job CARGA_TBACK_JDA_CT (queue SYS$NODE, entry 58) terminated with
    > error status
    >
    > %NONAME-W-NOMSG, Message number 00000000


    This means either:

    1. The .COM file that is the batch job has a $ EXIT 0 (or $ EXIT
    and symbol happens to have a 0 in it).

    or

    2. The .COM file has ON WARNING EXIT, and some command or
    application that the .COM file runs is exiting with a 0 status.

    In either case, the appropriate next step would be to put a SET VERIFY
    in the .COM file so that there is more information in the .LOG file.

    hth

    - Rob


    --

    Rob Brown b r o w n a t g m c l d o t c o m
    G. Michaels Consulting Ltd. (780)438-9343 (voice)
    Edmonton (780)437-3367 (FAX)
    http://gmcl.com/


+ Reply to Thread