Re: SOC 7 error while displaying S99 Fields in COBOL (WMQI 2.1)
this workedafter I specified the encoding and CCSID of input messsage's MQMD in the compute node to 500 and 785.I have the same test run for AS/400 as well.There was a problemfor packed signed number I get error in WMQI, 'parsing decimal data , no sign found'What should the CWF properties be for AS/400 RPG types like 4P2 and the value assigned is -12.34?Robert Broderick [EMAIL PROTECTED] wrote: That is what the doctor said and what the heavy meds are for!From: "Dawson, John" <[EMAIL PROTECTED]>Reply-To: MQSeries List <[EMAIL PROTECTED]>To: [EMAIL PROTECTED]Subject: Re: SOC 7 error while displaying S99 Fields in COBOL (WMQI 2.1)Date: Wed, 27 Aug 2003 11:36:56 -0500Bobbee, You passed the interview, but are you certified?Regards,John Dawson -Original Message-From: Robert Broderick [mailto:[EMAIL PROTECTED]Sent: Wednesday, August 27, 2003 11:21 AMTo: [EMAIL PROTECTED]Subject: Re: SOC 7 error while displaying S99 Fields in COBOL (WMQI2.1)The s99 field implies that the data in the sending field is a valid numericfield with the last byte containing a valid numeric sign.If my assembler isn't t rusty. What happens behind the the curtain isthat the compiler generates instructions to convert the Zone Decimal fieldto pack (which doesn't do a validate) and does a ZAP instruction whichtakesthe field down the hardware path where the numeric portion getinterrogated.That is where, I believe, the S0C7 is generated. SO.the sending fielsmust be a combination of the following F0-F9, C0-C9, D0-D9 there is anotherrange but I don't havv a green card available.I will take a further step in saying, and now I am streaching my brain,thatthe conversion from display format to the packed format to verify thenumeric portion DOES NOT care what is in the hig order signifigant signportion of the display characters. It just moves the digit portion. (egSDSDSD) until it gets to the last byte where it retrieves it's sign from.Soall the signs can be whatever except the last one which must be a C or D orF and the digits portion in ALL the Zone Decimal must be 0-9.DID I PASS THE TECH INTERVIEW?? (tee heehee)bobbee From: Ruzi R <[EMAIL PROTECTED]> Reply-To: MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: SOC 7 error while displaying S99 Fields in COBOL (WMQI 2.1) Date: Wed, 27 Aug 2003 08:50:26 -0700 Someone correct me if I am wrong It has been in the back of my mind that the S9 and COMP-3 fields have to be changed ,before they are MQPUTed, to flat PIC 9 s without the assumed sign and COMP-3, and that the assumed sign to be coded as a one byte separate filed -- for conversion purposes. No? Ruzi --- Juni Per <[EMAIL PROTECTED]>wrote: Hi , I have the following COBOL copy book imported into WMQI(2.1 WinNT) 06 TESTVARIABLES. 07 TESTINPUT. 08 INTEGERNOSIGN PIC 99. 08 INTEGERSIGNED PIC S99. 08 DECIMALNOSIGN PIC 99V99. 08 DECIMALSIGNED PIC S99V99. 08 COMP3NOSIGN PIC 99V99 COMP-3. 08 COMP3SIGNED PIC S99V99 COMP-3. I assign the following values to them in a compute node SET "OutputRoot"."MRM"."INTEGERNOSIGN" = 12; SET "OutputRoot"."MRM"."INTEGERSIGNED" = -12; SET "OutputRoot"."MRM"."DECIMALNOSIGN" = 1234; SET "OutputRoot"."MRM"."DECIMALSIGNED" = -1234; SET "OutputRoot"."MRM"."COMP3NOSIGN" = 5678; SET "OutputRoot"."MRM"."COMP3SIGNED" = -678; Now when a COBOL program on mainframe reads this message and moves into the same copybook and displays the fields , I get an SOC 7 error for the S99 field.WHat could be the problem. Pls respond. THanks in ADvance - Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive_Enter for your chance to IM with Bon Jovi, Seal, Bow Wow, or Mary J Bligeusing MSN Messenger http://entertainment.msn.com/imastarInstructions for managing your mailing list subscription are provided inthe Listserv General Users Guide available at http://www.lsoft.comArchive: http://vm.akh-wien.ac.at/MQSeries.archiveInstructions for managing your mailing list subscription are provided inthe Listserv General Users Guide available at http://www.lsoft.comArchive: http://vm.akh-wien.ac.at/MQSeries.archive_Enter for your chance to IM with Bon Jovi, Seal, Bow Wow, or Mary J Bligeusing MSN Messenger http://entertainment.msn.com/imastarInstructions for managing your mailing list subscription are provided inthe Listserv General Users Guide available at http://www.lsoft.comArchive: http://vm.akh-wien.ac.at/MQSeries.archive Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software
Re: REPOST@@@@@ !SOC 7 error while displaying S99 Fields in COBOL (WMQI 2.1)
this workedafter I specified the encoding and CCSID of input messsage's MQMD in the compute node to 500 and 785.I have the same test run for AS/400 as well.But it does'nt seem to work for packed signed number I get error in WMQI, 'parsing decimal data , no sign found'What should the CWF properties be for AS/400 RPG types like 4P2 and the value assigned is -12.34? Robert Broderick [EMAIL PROTECTED] wrote: That is what the doctor said and what the heavy meds are for!From: "Dawson, John" <[EMAIL PROTECTED]>Reply-To: MQSeries List <[EMAIL PROTECTED]>To: [EMAIL PROTECTED]Subject: Re: SOC 7 error while displaying S99 Fields in COBOL (WMQI 2.1)Date: Wed, 27 Aug 2003 11:36:56 -0500Bobbee, You passed the interview, but are you certified?Regards,John Dawson -Original Message-From: Robert Broderick [mailto:[EMAIL PROTECTED]Sent: Wednesday, August 27, 2003 11:21 AMTo: [EMAIL PROTECTED]Subject: Re: SOC 7 error while displaying S99 Fields in COBOL (WMQI2.1)The s99 field implies that the data in the sending field is a valid numericfield with the last byte containing a valid numeric sign.If my assembler isn't t rusty. What happens behind the the curtain isthat the compiler generates instructions to convert the Zone Decimal fieldto pack (which doesn't do a validate) and does a ZAP instruction whichtakesthe field down the hardware path where the numeric portion getinterrogated.That is where, I believe, the S0C7 is generated. SO.the sending fielsmust be a combination of the following F0-F9, C0-C9, D0-D9 there is anotherrange but I don't havv a green card available.I will take a further step in saying, and now I am streaching my brain,thatthe conversion from display format to the packed format to verify thenumeric portion DOES NOT care what is in the hig order signifigant signportion of the display characters. It just moves the digit portion. (egSDSDSD) until it gets to the last byte where it retrieves it's sign from.Soall the signs can be whatever except the last one which must be a C or D orF and the digits portion in ALL the Zone Decimal must be 0-9.DID I PASS THE TECH INTERVIEW?? (tee heehee)bobbee From: Ruzi R <[EMAIL PROTECTED]> Reply-To: MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: SOC 7 error while displaying S99 Fields in COBOL (WMQI 2.1) Date: Wed, 27 Aug 2003 08:50:26 -0700 Someone correct me if I am wrong It has been in the back of my mind that the S9 and COMP-3 fields have to be changed ,before they are MQPUTed, to flat PIC 9 s without the assumed sign and COMP-3, and that the assumed sign to be coded as a one byte separate filed -- for conversion purposes. No? Ruzi --- Juni Per <[EMAIL PROTECTED]>wrote: Hi , I have the following COBOL copy book imported into WMQI(2.1 WinNT) 06 TESTVARIABLES. 07 TESTINPUT. 08 INTEGERNOSIGN PIC 99. 08 INTEGERSIGNED PIC S99. 08 DECIMALNOSIGN PIC 99V99. 08 DECIMALSIGNED PIC S99V99. 08 COMP3NOSIGN PIC 99V99 COMP-3. 08 COMP3SIGNED PIC S99V99 COMP-3. I assign the following values to them in a compute node SET "OutputRoot"."MRM"."INTEGERNOSIGN" = 12; SET "OutputRoot"."MRM"."INTEGERSIGNED" = -12; SET "OutputRoot"."MRM"."DECIMALNOSIGN" = 1234; SET "OutputRoot"."MRM"."DECIMALSIGNED" = -1234; SET "OutputRoot"."MRM"."COMP3NOSIGN" = 5678; SET "OutputRoot"."MRM"."COMP3SIGNED" = -678; Now when a COBOL program on mainframe reads this message and moves into the same copybook and displays the fields , I get an SOC 7 error for the S99 field.WHat could be the problem. Pls respond. THanks in ADvance - Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive_Enter for your chance to IM with Bon Jovi, Seal, Bow Wow, or Mary J Bligeusing MSN Messenger http://entertainment.msn.com/imastarInstructions for managing your mailing list subscription are provided inthe Listserv General Users Guide available at http://www.lsoft.comArchive: http://vm.akh-wien.ac.at/MQSeries.archiveInstructions for managing your mailing list subscription are provided inthe Listserv General Users Guide available at http://www.lsoft.comArchive: http://vm.akh-wien.ac.at/MQSeries.archive_Enter for your chance to IM with Bon Jovi, Seal, Bow Wow, or Mary J Bligeusing MSN Messenger http://entertainment.msn.com/imastarInstructions for managing your mailing list subscription are provided inthe Listserv General Users Guide available at http://www.lsoft.comArchive: http://vm.akh-wien.ac.at/MQSeries.archive Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software
Re: SOC 7 error while displaying S99 Fields in COBOL (WMQI 2.1)
That is what the doctor said and what the heavy meds are for! From: Dawson, John [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: SOC 7 error while displaying S99 Fields in COBOL (WMQI 2.1) Date: Wed, 27 Aug 2003 11:36:56 -0500 Bobbee, You passed the interview, but are you certified? Regards, John Dawson -Original Message- From: Robert Broderick [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 27, 2003 11:21 AM To: [EMAIL PROTECTED] Subject:Re: SOC 7 error while displaying S99 Fields in COBOL (WMQI 2.1) The s99 field implies that the data in the sending field is a valid numeric field with the last byte containing a valid numeric sign. If my assembler isn't t rusty. What happens behind the the curtain is that the compiler generates instructions to convert the Zone Decimal field to pack (which doesn't do a validate) and does a ZAP instruction which takes the field down the hardware path where the numeric portion get interrogated. That is where, I believe, the S0C7 is generated. SO.the sending fiels must be a combination of the following F0-F9, C0-C9, D0-D9 there is another range but I don't havv a green card available. I will take a further step in saying, and now I am streaching my brain, that the conversion from display format to the packed format to verify the numeric portion DOES NOT care what is in the hig order signifigant sign portion of the display characters. It just moves the digit portion. (eg SDSDSD) until it gets to the last byte where it retrieves it's sign from. So all the signs can be whatever except the last one which must be a C or D or F and the digits portion in ALL the Zone Decimal must be 0-9. DID I PASS THE TECH INTERVIEW?? (tee hee hee) bobbee From: Ruzi R [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: SOC 7 error while displaying S99 Fields in COBOL (WMQI 2.1) Date: Wed, 27 Aug 2003 08:50:26 -0700 Someone correct me if I am wrong It has been in the back of my mind that the S9 and COMP-3 fields have to be changed ,before they are MQPUTed, to flat PIC 9 s without the assumed sign and COMP-3, and that the assumed sign to be coded as a one byte separate filed -- for conversion purposes. No? Ruzi --- Juni Per [EMAIL PROTECTED] wrote: Hi , I have the following COBOL copy book imported into WMQI(2.1 WinNT) 06 TESTVARIABLES. 07 TESTINPUT. 08 INTEGERNOSIGN PIC 99. 08 INTEGERSIGNED PIC S99. 08 DECIMALNOSIGN PIC 99V99. 08 DECIMALSIGNED PIC S99V99. 08 COMP3NOSIGN PIC 99V99 COMP-3. 08 COMP3SIGNED PIC S99V99 COMP-3. I assign the following values to them in a compute node SET OutputRoot.MRM.INTEGERNOSIGN = 12; SET OutputRoot.MRM.INTEGERSIGNED = -12; SET OutputRoot.MRM.DECIMALNOSIGN = 1234; SET OutputRoot.MRM.DECIMALSIGNED = -1234; SET OutputRoot.MRM.COMP3NOSIGN = 5678; SET OutputRoot.MRM.COMP3SIGNED = -678; Now when a COBOL program on mainframe reads this message and moves into the same copybook and displays the fields , I get an SOC 7 error for the S99 field.WHat could be the problem. Pls respond. THanks in ADvance - Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive _ Enter for your chance to IM with Bon Jovi, Seal, Bow Wow, or Mary J Blige using MSN Messenger http://entertainment.msn.com/imastar Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive _ Enter for your chance to IM with Bon Jovi, Seal, Bow Wow, or Mary J Blige using MSN Messenger http://entertainment.msn.com/imastar Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
SOC 7 error while displaying S99 Fields in COBOL (WMQI 2.1)
Hi , I have the following COBOL copy book imported into WMQI(2.1 WinNT) 06 TESTVARIABLES. 07 TESTINPUT. 08 INTEGERNOSIGN PIC 99. 08 INTEGERSIGNED PIC S99. 08 DECIMALNOSIGN PIC 99V99. 08 DECIMALSIGNED PIC S99V99. 08 COMP3NOSIGN PIC 99V99 COMP-3. 08 COMP3SIGNED PIC S99V99 COMP-3. I assign the following values to them in a compute node SET "OutputRoot"."MRM"."INTEGERNOSIGN" = 12; SET "OutputRoot"."MRM"."INTEGERSIGNED" = -12; SET "OutputRoot"."MRM"."DECIMALNOSIGN" = 1234; SET "OutputRoot"."MRM"."DECIMALSIGNED" = -1234; SET "OutputRoot"."MRM"."COMP3NOSIGN" = 5678; SET "OutputRoot"."MRM"."COMP3SIGNED" = -678; Now when a COBOL program on mainframe reads this message and moves into the same copybook and displays the fields ,I get an SOC 7 error for the S99 field.WHat could be the problem. Pls respond. THanks in ADvance Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month!
Re: SOC 7 error while displaying S99 Fields in COBOL (WMQI 2.1)
What does the MQ message look like? Can you post a hex dump of the record??? bb PS Keep the layout in the REPLY From: Juni Per [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: SOC 7 error while displaying S99 Fields in COBOL (WMQI 2.1) Date: Tue, 26 Aug 2003 21:58:29 -0700 Hi , I have the following COBOL copy book imported into WMQI(2.1 WinNT) 06 TESTVARIABLES. 07 TESTINPUT. 08 INTEGERNOSIGN PIC 99. 08 INTEGERSIGNED PIC S99. 08 DECIMALNOSIGN PIC 99V99. 08 DECIMALSIGNED PIC S99V99. 08 COMP3NOSIGN PIC 99V99 COMP-3. 08 COMP3SIGNED PIC S99V99 COMP-3. I assign the following values to them in a compute node SET OutputRoot.MRM.INTEGERNOSIGN = 12; SET OutputRoot.MRM.INTEGERSIGNED = -12; SET OutputRoot.MRM.DECIMALNOSIGN = 1234; SET OutputRoot.MRM.DECIMALSIGNED = -1234; SET OutputRoot.MRM.COMP3NOSIGN = 5678; SET OutputRoot.MRM.COMP3SIGNED = -678; Now when a COBOL program on mainframe reads this message and moves into the same copybook and displays the fields , I get an SOC 7 error for the S99 field.WHat could be the problem. Pls respond. THanks in ADvance - Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! _ Enter for your chance to IM with Bon Jovi, Seal, Bow Wow, or Mary J Blige using MSN Messenger http://entertainment.msn.com/imastar Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: SOC 7 error while displaying S99 Fields in COBOL (WMQI 2.1)
Someone correct me if I am wrong It has been in the back of my mind that the S9 and COMP-3 fields have to be changed ,before they are MQPUTed, to flat PIC 9 s without the assumed sign and COMP-3, and that the assumed sign to be coded as a one byte separate filed -- for conversion purposes. No? Ruzi --- Juni Per [EMAIL PROTECTED] wrote: Hi , I have the following COBOL copy book imported into WMQI(2.1 WinNT) 06 TESTVARIABLES. 07 TESTINPUT. 08 INTEGERNOSIGN PIC 99. 08 INTEGERSIGNED PIC S99. 08 DECIMALNOSIGN PIC 99V99. 08 DECIMALSIGNED PIC S99V99. 08 COMP3NOSIGN PIC 99V99 COMP-3. 08 COMP3SIGNED PIC S99V99 COMP-3. I assign the following values to them in a compute node SET OutputRoot.MRM.INTEGERNOSIGN = 12; SET OutputRoot.MRM.INTEGERSIGNED = -12; SET OutputRoot.MRM.DECIMALNOSIGN = 1234; SET OutputRoot.MRM.DECIMALSIGNED = -1234; SET OutputRoot.MRM.COMP3NOSIGN = 5678; SET OutputRoot.MRM.COMP3SIGNED = -678; Now when a COBOL program on mainframe reads this message and moves into the same copybook and displays the fields , I get an SOC 7 error for the S99 field.WHat could be the problem. Pls respond. THanks in ADvance - Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: SOC 7 error while displaying S99 Fields in COBOL (WMQI 2.1)
The s99 field implies that the data in the sending field is a valid numeric field with the last byte containing a valid numeric sign. If my assembler isn't t rusty. What happens behind the the curtain is that the compiler generates instructions to convert the Zone Decimal field to pack (which doesn't do a validate) and does a ZAP instruction which takes the field down the hardware path where the numeric portion get interrogated. That is where, I believe, the S0C7 is generated. SO.the sending fiels must be a combination of the following F0-F9, C0-C9, D0-D9 there is another range but I don't havv a green card available. I will take a further step in saying, and now I am streaching my brain, that the conversion from display format to the packed format to verify the numeric portion DOES NOT care what is in the hig order signifigant sign portion of the display characters. It just moves the digit portion. (eg SDSDSD) until it gets to the last byte where it retrieves it's sign from. So all the signs can be whatever except the last one which must be a C or D or F and the digits portion in ALL the Zone Decimal must be 0-9. DID I PASS THE TECH INTERVIEW?? (tee hee hee) bobbee From: Ruzi R [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: SOC 7 error while displaying S99 Fields in COBOL (WMQI 2.1) Date: Wed, 27 Aug 2003 08:50:26 -0700 Someone correct me if I am wrong It has been in the back of my mind that the S9 and COMP-3 fields have to be changed ,before they are MQPUTed, to flat PIC 9 s without the assumed sign and COMP-3, and that the assumed sign to be coded as a one byte separate filed -- for conversion purposes. No? Ruzi --- Juni Per [EMAIL PROTECTED] wrote: Hi , I have the following COBOL copy book imported into WMQI(2.1 WinNT) 06 TESTVARIABLES. 07 TESTINPUT. 08 INTEGERNOSIGN PIC 99. 08 INTEGERSIGNED PIC S99. 08 DECIMALNOSIGN PIC 99V99. 08 DECIMALSIGNED PIC S99V99. 08 COMP3NOSIGN PIC 99V99 COMP-3. 08 COMP3SIGNED PIC S99V99 COMP-3. I assign the following values to them in a compute node SET OutputRoot.MRM.INTEGERNOSIGN = 12; SET OutputRoot.MRM.INTEGERSIGNED = -12; SET OutputRoot.MRM.DECIMALNOSIGN = 1234; SET OutputRoot.MRM.DECIMALSIGNED = -1234; SET OutputRoot.MRM.COMP3NOSIGN = 5678; SET OutputRoot.MRM.COMP3SIGNED = -678; Now when a COBOL program on mainframe reads this message and moves into the same copybook and displays the fields , I get an SOC 7 error for the S99 field.WHat could be the problem. Pls respond. THanks in ADvance - Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive _ Enter for your chance to IM with Bon Jovi, Seal, Bow Wow, or Mary J Blige using MSN Messenger http://entertainment.msn.com/imastar Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: SOC 7 error while displaying S99 Fields in COBOL (WMQI 2.1)
Bobbee, You passed the interview, but are you certified? Regards, John Dawson -Original Message- From: Robert Broderick [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 27, 2003 11:21 AM To: [EMAIL PROTECTED] Subject:Re: SOC 7 error while displaying S99 Fields in COBOL (WMQI 2.1) The s99 field implies that the data in the sending field is a valid numeric field with the last byte containing a valid numeric sign. If my assembler isn't t rusty. What happens behind the the curtain is that the compiler generates instructions to convert the Zone Decimal field to pack (which doesn't do a validate) and does a ZAP instruction which takes the field down the hardware path where the numeric portion get interrogated. That is where, I believe, the S0C7 is generated. SO.the sending fiels must be a combination of the following F0-F9, C0-C9, D0-D9 there is another range but I don't havv a green card available. I will take a further step in saying, and now I am streaching my brain, that the conversion from display format to the packed format to verify the numeric portion DOES NOT care what is in the hig order signifigant sign portion of the display characters. It just moves the digit portion. (eg SDSDSD) until it gets to the last byte where it retrieves it's sign from. So all the signs can be whatever except the last one which must be a C or D or F and the digits portion in ALL the Zone Decimal must be 0-9. DID I PASS THE TECH INTERVIEW?? (tee hee hee) bobbee From: Ruzi R [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: SOC 7 error while displaying S99 Fields in COBOL (WMQI 2.1) Date: Wed, 27 Aug 2003 08:50:26 -0700 Someone correct me if I am wrong It has been in the back of my mind that the S9 and COMP-3 fields have to be changed ,before they are MQPUTed, to flat PIC 9 s without the assumed sign and COMP-3, and that the assumed sign to be coded as a one byte separate filed -- for conversion purposes. No? Ruzi --- Juni Per [EMAIL PROTECTED] wrote: Hi , I have the following COBOL copy book imported into WMQI(2.1 WinNT) 06 TESTVARIABLES. 07 TESTINPUT. 08 INTEGERNOSIGN PIC 99. 08 INTEGERSIGNED PIC S99. 08 DECIMALNOSIGN PIC 99V99. 08 DECIMALSIGNED PIC S99V99. 08 COMP3NOSIGN PIC 99V99 COMP-3. 08 COMP3SIGNED PIC S99V99 COMP-3. I assign the following values to them in a compute node SET OutputRoot.MRM.INTEGERNOSIGN = 12; SET OutputRoot.MRM.INTEGERSIGNED = -12; SET OutputRoot.MRM.DECIMALNOSIGN = 1234; SET OutputRoot.MRM.DECIMALSIGNED = -1234; SET OutputRoot.MRM.COMP3NOSIGN = 5678; SET OutputRoot.MRM.COMP3SIGNED = -678; Now when a COBOL program on mainframe reads this message and moves into the same copybook and displays the fields , I get an SOC 7 error for the S99 field.WHat could be the problem. Pls respond. THanks in ADvance - Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive _ Enter for your chance to IM with Bon Jovi, Seal, Bow Wow, or Mary J Blige using MSN Messenger http://entertainment.msn.com/imastar Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: SOC 7 error while displaying S99 Fields in COBOL (WMQI 2.1)
That's correct. Signed decimal and packed fields do not survive data conversion. The best practice is that a message should be all binary and not converted or all character if it needs to be converted. Bottom line--all fields in the message should be defined in display formats (PIC X or PIC 9...). -Original Message- From: Ruzi R [SMTP:[EMAIL PROTECTED] Sent: Wednesday, August 27, 2003 8:50 AM To: [EMAIL PROTECTED] Subject: Re: SOC 7 error while displaying S99 Fields in COBOL (WMQI 2.1) Someone correct me if I am wrong It has been in the back of my mind that the S9 and COMP-3 fields have to be changed ,before they are MQPUTed, to flat PIC 9 s without the assumed sign and COMP-3, and that the assumed sign to be coded as a one byte separate filed -- for conversion purposes. No? Ruzi --- Juni Per [EMAIL PROTECTED] wrote: Hi , I have the following COBOL copy book imported into WMQI(2.1 WinNT) 06 TESTVARIABLES. 07 TESTINPUT. 08 INTEGERNOSIGN PIC 99. 08 INTEGERSIGNED PIC S99. 08 DECIMALNOSIGN PIC 99V99. 08 DECIMALSIGNED PIC S99V99. 08 COMP3NOSIGN PIC 99V99 COMP-3. 08 COMP3SIGNED PIC S99V99 COMP-3. I assign the following values to them in a compute node SET OutputRoot.MRM.INTEGERNOSIGN = 12; SET OutputRoot.MRM.INTEGERSIGNED = -12; SET OutputRoot.MRM.DECIMALNOSIGN = 1234; SET OutputRoot.MRM.DECIMALSIGNED = -1234; SET OutputRoot.MRM.COMP3NOSIGN = 5678; SET OutputRoot.MRM.COMP3SIGNED = -678; Now when a COBOL program on mainframe reads this message and moves into the same copybook and displays the fields , I get an SOC 7 error for the S99 field.WHat could be the problem. Pls respond. THanks in ADvance - Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: SOC 7 error while displaying S99 Fields in COBOL (WMQI 2.1)
The INTEGERSIGNED field (if memory serves me correctly) is treated as a Zoned Decimal field. In other words, the low order byte will have the high order 4 bits set to C for positive and D for negative numbers (system preferred signs). I can't remember if it accepts A and F for positive and B for negative as well. Packed decimal arithmetic will accept any of the A through F bit configurations in the sign position. It sounds like what is getting passed across and converted in the sign position on the host side is resulting in a bit configuration of 0 through 9 accounting for the data exception (S0C7). Cheers... Jim Nuckolls Juni Per wrote: Hi , I have the following COBOL copy book imported into WMQI(2.1 WinNT) 06 TESTVARIABLES. 07 TESTINPUT. 08 INTEGERNOSIGN PIC 99. 08 INTEGERSIGNED PIC S99. 08 DECIMALNOSIGN PIC 99V99. 08 DECIMALSIGNED PIC S99V99. 08 COMP3NOSIGN PIC 99V99 COMP-3. 08 COMP3SIGNED PIC S99V99 COMP-3. I assign the following values to them in a compute node SET OutputRoot.MRM.INTEGERNOSIGN = 12; SET OutputRoot.MRM.INTEGERSIGNED = -12; SET OutputRoot.MRM.DECIMALNOSIGN = 1234; SET OutputRoot.MRM.DECIMALSIGNED = -1234; SET OutputRoot.MRM.COMP3NOSIGN = 5678; SET OutputRoot.MRM.COMP3SIGNED = -678; Now when a COBOL program on mainframe reads this message and moves into the same copybook and displays the fields , I get an SOC 7 error for the S99 field.WHat could be the problem. Pls respond. THanks in ADvance Do you Yahoo!? SBC Yahoo! DSL http://pa.yahoo.com/*http://rd.yahoo.com/evt=1207/*http://promo.yahoo.com/sbc/ - Now only $29.95 per month! Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
