ibmi-brunch-learn

Announcement

Collapse
No announcement yet.

How do I automatically answer a message waiting??

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • How do I automatically answer a message waiting??

    Hi,

    I need to automatically answer a message waiting IFS1007 with a R. How do I accomplish this?

    IFS1007 received by procedure BLDDLYSUMC. (C D I R) BLDDLYSUM/EMCPGMR/399264

    Thanks,

    DAC

  • #2
    Re: How do I automatically answer a message waiting??

    Hi Dac:

    Look at WRKRPYLE ...... but be careful with this it will ALWAYS reply using the chosen response.

    I beleive you can "addrplye" and "rmvrplye" in a cl program etc .... but Again
    while the command is active ALL jobs will use that reply to the error.

    Best of Luck
    GLS
    The problem with quotes on the internet is that it is hard to verify their authenticity.....Abraham Lincoln

    Comment


    • #3
      Re: How do I automatically answer a message waiting??

      SNDRPY or using the send reply API may be a better solution for this...
      I'm not anti-social, I just don't like people -Tommy Holden

      Comment


      • #4
        Re: How do I automatically answer a message waiting??

        My first choice would be to use MONITOR to trap the error in the program itself. Only if it's a program that you can't change (because you don't have the source, or whatever) would I consider using something like an auto-reply entry or having a program that does a SNDRPY.

        Just my opinion.

        Comment


        • #5
          Re: How do I automatically answer a message waiting??

          A system reply list entry shouldn't apply to ALL jobs in the system unless someone configured things that way. The system reply list should only apply to jobs that run with the INQMSGRPY(*SYSRPYL) attribute set. By default, jobs should run as INQMSGRPY(*RQD).

          Also, depending on what IFS1007 is, its message data might be tested in the reply list entry so that it only affected this job, even if other jobs also used *SYSRPYL.

          Regardless, an automatic 'R' seems like trouble. If the process is fast enough and the condition isn't cleared quickly, the job could execute a whole bunch of "retries" in just a few seconds.

          That's one good reason for a MONITOR-block. There are others.

          Tom
          Tom

          There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors.

          Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?

          Comment

          Working...
          X