×
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.
You may look at www.rpgiv.info site and select RPG codes and select send message to program or click following link.
http://rpgiv.info/mambo/index.php?option=com_content&task=view&id=82&Itemid=40
Regards,
Chamara Withanachchi
IBM Certified Power System Expert
RPG Programmer
(owner of www.rpgiv.info)
WWW.RPGIV.INFO
Mob: +971 50 5698644
Tel: +971 6 5595887
chamaraw@xxxxxxxxxx
www.rpgiv.info
i want to be future ready. i want control. i want an i.
Sent from my BlackBerry® wireless device
-----Original Message-----
From: John McKee <jmmckee@xxxxxxxxxxxxxx>
Date: Wed, 13 May 2009 11:47:11
To: Midrange Systems Technical Discussion<midrange-l@xxxxxxxxxxxx>
Subject: Parameter issues using QMHSNDPM API
I used teh following QSH command:
system 'call pgm(qmhsndpm) parm('CPF9898' 'QCPFMSG *LIBL' 'TEST MESSAGE' '1
2' '*ESCAPE' '*SYSOPR' '3' ' ' ' ')'
CPF24B3: Message type MESSAGE not valid.
CPC2206: Ownership of object QZSHSYSTEM in QTEMP type *USRSPC changed.
Issues I have: No idea what should be used just after the *SYSOPR parameter.
Coding a 3 is just guesswork.
Is the CPF24B3 related to the value of '3'? The command SNDPGMMSG does not show
a MESSAGE parameter.
I was wondering if SNDPGMMSG was restricted based on a parameter, but the API
that actually sends the message did not need that restriction.
John McKee
midrange.com
