|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
WebSphere MQ - Z/OS Mainframe Challenge |
« View previous topic :: View next topic » |
Author |
Message
|
bruce2359 |
Posted: Sun May 18, 2014 1:20 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Kenzi wrote: |
Quote: |
********************************************************
Mainframe Challenge - Credit card payment unit test tool
********************************************************
Incorrect usage!
Program Usage
-------------
PAYMENT <queue manager> <cics request queue> <reply queue> <userid> <payment value> <payment description>
The payment description has a maximum length of 35 characters.
The monetary value must be within the range 0.01 - 9999.99. |
The monetary value must be within the range 0.01 - 9999.99. [/code]
I checked my account on CICS and really is not updating the balance to 100.00... |
Given the error messages in the SYSOUT (above), no surprise that it didn't work. Like most things on computers (including Windows and UNIX), you must supply data that conforms precisely to the program specifications.
The bold line above seems to be telling you the correct format and syntax for the data to be passed to the program. Your PARM is CSV (comma delimited values), but the bold line has spaces, not commas.
You provided this PARM data.
Quote: |
PARM='CSQ1,CARD.PAYMENTS,<userID>.REPLY,<userID>,100.00,"PAY"' |
Does the PARM values you provided conform to the program requirements of valid data?
You seem to have access to the requirements, not us. Keep in mind that there is no mainframe-wide data format, data type, or data usage convention. Just as in Windows/UNIX, it's all up to the individual application program, and the users of that program, to communicate with each other. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Last edited by bruce2359 on Sun May 18, 2014 2:01 pm; edited 2 times in total |
|
Back to top |
|
 |
bruce2359 |
Posted: Sun May 18, 2014 1:51 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Moved to Mainframe forum. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
Kenzi |
Posted: Sun May 18, 2014 7:12 pm Post subject: |
|
|
Newbie
Joined: 16 May 2014 Posts: 7
|
BRUCE!!! Thank you!!!!!!
the JCL code was delivered faulty and my goal was to consult reference materials and fix it!
I saw a lot about PARM, as this example line in the material:
http://publib.boulder.ibm.com/infocenter/zvm/v5r4/index.jsp?topic=/com.ibm.zos.r9.ieab100/jclexs.htm
//BIND EXEC PGM=IEWL,
// PARM='linect=55,list(all),map,xref,options=optndd,wkspa
// ce=(400,10000)'
Looking over this example, I've decided to write the parameters, separated by commas, not space >_>
Thank you so much!! |
|
Back to top |
|
 |
bruce2359 |
Posted: Sun May 18, 2014 8:48 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
PARM in an EXEC statement (in your example) is the z/OS method of passing parameters to an application. It's up to the application how it receives and processes the passed parameters, if it does so at all.
HEWL/IEWL is the linkage editor (binder) - just another program that can take PARMs to set/override default application behaviors. z/OS IBM-supplied utilities (of which IEWL is one) most often use commas to separate PARM values. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|