RE: How to personalize System Request Menu? Great! -- MIDRANGE-L

Or

5) Shucks...why didn't I think of that <g>

I like Robins idea....It's works.

</flame retardant suit on>



 -----Original Message-----
From:   barsa@barsaconsulting.com [mailto:barsa@barsaconsulting.com]
Sent:   Friday, December 28, 2001 12:14 PM
To:     midrange-l@midrange.com
Subject:        RE: How to personalize System Request Menu? Great!


I don't like the idea for a couple of reasons:

1).  It has to be done for each new release.  (There is an exposure that
IBM could update that message mid-release via PTF, but this is unusual.)
2).  IBM has been known to modify the message from release to release.  If
you don't carefully follow what they do, you could cause breakage.
3).  It's easy to screw up.
4).  A malicious command could always be inserted.

Al

Al Barsa, Jr.
Barsa Consulting Group, LLC

400>390

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.com






                    "Robin Coles"
                    <robin@ringbase.com       To:
<midrange-l@midrange.com>
                    >                         cc:
                    Sent by:                  Subject:     RE: How to
personalize System Request Menu? Great!
                    midrange-l-admin@mi
                    drange.com


                    12/28/01 01:00 PM
                    Please respond to
                    midrange-l






> Cheers, could be a really kind if U can provide me with the
> example. Because of the urgency of the implementation,
> example could be a great help!


I'm not clear on what Al Barsa doesn't like about the suggestion - this
is what I do, but I'm happy to bow to Al's knowledge and experience if
it's something dim....

I did a CRTMSGF to create a message file in my library called TOOLMSG.

I did a MRGMSGF to move in CPX2313 from QCPFMSG, and amended it to look
like this:

                         Display Formatted Message Text

                                                             System:
CAM
 Message ID . . . . . . . . . :   CPX2313

 Message file . . . . . . . . :   TOOLMSG

   Library  . . . . . . . . . :     ROBIN



 Message . . . . :   ENDRQS     WRKJOB     DSPMSG     SNDMSG     SIGNOFF

   DSPMSG     DSCJOB     CMDENT


CMDENT is my own command to call command entry.  It just takes a single
parameter.  The command and CPP are:

CMD
PARM       KWD(DUMMY) TYPE(*CHAR) LEN(10)


PGM PARM(&JUNK)
DCL &JUNK *CHAR 10
TFRCTL QCMD
ENDPGM

You could have the CL display a screen or whatever you needed.

My initial program does an OVRMSGF of QCPFMSG to TOOLMSG.  Any messages
not in TOOLMSG will still be retrieved from QCPFMSG.  The statement is:

OVRMSGF MSGF(QCPFMSG) TOMSGF(ROBIN/TOOLMSG) SECURE(*YES)

As long as the override stays in scope, sysreq-7 gives me command entry
and sysreq 3 gives me workjob instead of dspjob.  This method is
independent of OS releases (although it would be best to check CPX2313
for a change) - I've been running the same code since V3R2.

If you have access to News400's site, a better written up version was
published under the title "Message File Frivolity" in the December 2000
issue.  The site won't let me in at the moment to give the URL.

Any questions, please ask.
Cheers
Robin

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.