Re: Adding commands to stack (F9)?

[jmoreno@xxxxxxxxxxxxxxxx]

Hi David.
     I understand your requiriment. In the past I've seen User Defined
Programs that execute the commands but cannot make them part of the message
queue for the running job. Well the Object ~ so speaking is QJOBMSGQ but it
is not addressable because the object is part of your Job Structure but it
is not one of the AS/400 Objects (You Know Type / Subtype ... Blah Blah
Blah). Just run the DMPJOB command and with quick HEX values you will see
what I am talking
about.---------------------------------------------------------------------
---------------------------------------------------------------------------
---------------------------The problem with User defined Command processors
is that you can not do STUFF like the mask/protect  passwords during the
retrieval process --- Whats wrong with QUSCMDLN on demand (F9 will work
...) ?
---------------------------------------------------------------------------
---------------------------------------------------------------------------
------------------------------Maybe a User Defined Program to throw
messages Type *RQS to the QCMD Program Command Processor. You Know
.....SNDPGMMSG   MSGTYPE(*RQS )  MSG(&MSG) TOPGMQ(*EXT) Where &MSG is your
Command. But there is problems with this approach: Program Stack Overrides
and other Job Stacking Issues .... Well those are my two cents
---------------------------------------------------------------------------
---------------------------------------------------------------------------
------------------------------A while back I submitted a requirement at the
COMMON conference to Enhance the API QUSCMDLN to allow Row / Column/ /
Wrapp Support. But did not get many votes. Good luck David.


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---