× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Simple Console
  • From: Rob Berendt <rob@xxxxxxxxx>
  • Date: Thu, 20 Jan 2000 12:55:15 -0500

You could use an API that checks for any jobs that run for 
you under QINTER or QCTL and sends them to that job name.  
The job name should be the same as the workstation name.  I 
think the API is QUSLJOB.




leslier@datrek.com on 01/20/2000 12:51:53 PM
Please respond to MIDRANGE-L@midrange.com@Internet
To:     MIDRANGE-L@midrange.com@Internet
cc:      
Fax to: 
Subject:        Re: Simple Console

One caveat. I forgot to mention that when I log on my initial program
makes an entry for each new session in the SESSIONS data area and adds
one to the number in the SESCNT data area.

"L. S. Russell" wrote:
> 
>  *************** Beginning of data *************************************
> I wrote this to send messages to all my sessions. I got tired of being
> unaware that there was a message waiting for me on another session. I
> attached this cl to my message queue using the PGM parameter on the
> CHGMSGQ command. I set my message queue to break (not sure it will work
> otherwise).
> I set up a data area named SESSIONS that keeps track of the sessions I
> am logged onto, and on called SESCNT that keeps a number of sessions.
> You can modify this to work with QSYSOPR's message queue. But I will
> leave that up to you.
> 
>   /*-----------------------------------------------------------------*/
>   /* Objective: Monitor user message queue, send messages to device  */
>   /*            names found in SESSIONS data area.                   */
>   /*-----------------------------------------------------------------*/
>               PGM        PARM(&MSGQ &QLIB &MSGREF)
> 
>               DCL        VAR(&MSGQ) TYPE(*CHAR) LEN(10)
>               DCL        VAR(&QLIB) TYPE(*CHAR) LEN(10)
>               DCL        VAR(&MSGREF) TYPE(*CHAR) LEN(4)
>               DCL        VAR(&MSG) TYPE(*CHAR) LEN(132)
>               DCL        VAR(&SESSIONS) TYPE(*CHAR) LEN(1000)
>               DCL        VAR(&SES1) TYPE(*CHAR) LEN(10)
>               DCL        VAR(&SES2) TYPE(*CHAR) LEN(10)
>               DCL        VAR(&SES3) TYPE(*CHAR) LEN(10)
> 
>              RTVDTAARA  DTAARA(LESLIER/SESSIONS) RTNVAR(&SESSIONS)
>              CHGVAR     VAR(&SES1) VALUE(%SST(&SESSIONS 1 10))
>              CHGVAR     VAR(&SES2) VALUE(%SST(&SESSIONS 11 10))
>              CHGVAR     VAR(&SES3) VALUE(%SST(&SESSIONS 21 10))
> 
>              RCVMSG     MSGQ(&QLIB/&MSGQ) MSGKEY(&MSGREF) MSG(&MSG)
> 
>              IF         COND(&SES1 *NE ' ') THEN(DO)
>              SBMJOB     CMD(SNDBRKMSG MSG(&MSG) TOMSGQ(&SES1)) LOG(0 +
>                           0 *NOLIST) MSGQ(*NONE)
>              ENDDO
> 
>              IF         COND(&SES2 *NE ' ') THEN(DO)
>              SBMJOB     CMD(SNDBRKMSG MSG(&MSG) TOMSGQ(&SES2)) LOG(0 +
>                           0 *NOLIST) MSGQ(*NONE)
>              ENDDO
> 
>              IF         COND(&SES3 *NE ' ') THEN(DO)
>              SBMJOB     CMD(SNDBRKMSG MSG(&MSG) TOMSGQ(&SES3)) LOG(0 +
>                           0 *NOLIST) MSGQ(*NONE)
>              ENDDO
> 
> 
> ENDPGM
> 
> 
> Bob Randall wrote:
> >
> > We have had an AS/400 for about 1.5 years now. Before that we had a
> > System36. I come from an extensive mainframe background. Unfortunately we
> > had no AS/400 experience, and no training. Boy is that the wrong way to do
> > things! Except for the AS/400, we have always known systems to have
> > "dedicated" consoles that roll the system messages past. That way messages
> > that need responses are not "missed". Is there a similar feature on the
> > AS/400 that I just don't know about?
> >
> > Thanks,
> > Bob
> >
> > +---
> > | This is the Midrange System Mailing List!
> > | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
> > | Questions should be directed to the list owner/operator: 
>david@midrange.com
> > +---
> 
> --
> L. S. Russell Programmer/Analyst
> Datrek Professional Bags, Inc.
> 2413 Industrial Drive
> Springfield, TN. 37172
> mailto:leslier@datrek.com
> http://www.datrek.com
> --
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: david@midrange.com
> +---

--
L. S. Russell Programmer/Analyst
Datrek Professional Bags, Inc.
2413 Industrial Drive
Springfield, TN. 37172
mailto:leslier@datrek.com
http://www.datrek.com
--
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.