The error message is not referring to the BINDSYS step, but to the BINDSYS
procstep of the DB2COB step executing the COMP006L procedure.
regards,
Gunnar
- Original Message -
From: "Sérgio Lima Costa"
Newsgroups: bit.listserv.ibm-main
To:
Sent: Thursday, May 26, 2011 10:35 PM
Subject:
- Original Message -
From: "john gilmore"
Newsgroups: bit.listserv.ibm-main
To:
Sent: Monday, January 11, 2010 9:20 PM
Subject: Re: Bad leap-year code
>
> It is certainly true, as Joel C. Ewing contends, that bad leap-year code
abounds. Unfortunately, it is also true that the assorted
If you add two zeros, to express the amount in dollars and cents, and then
convert to hex, you get 2020202020201250.
Two suggestions:
- mainframe EDIT pattern digit selectors (x'20') mis-expressed as characters
('20').
- ascii blanks (0x20) as fillers, mis-expressed as characters ("20").
regards
G
Seems like a strange action of the e-mail program (Binyamin's?), putting the
Message-ID concatenated to the Subject field in the reply.
Gunnar
- Original Message -
From: "Tom Marchant" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To:
Sent: Tuesday, April 08, 2008 3:01 PM
Subjec
Then I will have to check if this intercept routine may be the guilty one.
Thanks Jim, for putting me on track.
And thanks Chuck for the specific reference to a product.
I am just responsible for the application that suffered. I will ask the systems
people tomorrow if they have the named product
Thanks for the hint.
I tried TEST with L 10.%+C4%+7C% L(12) C and got .00..SSS2HKR
Does that indicate interception?
The level is SP7.0.9 FMID HBB740
- Original Message -
From: "Jim Mulder" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To:
Sent: Monday, April 07, 2008 10:03 PM
Sub
We have a problem with an application that use the SMFEWTM macro in 24-bit mode.
When used on z/OS 1.9 it seems that the return is made in 31-bit mode. Has
anyone else encountered this?
--
For IBM-MAIN subscribe / signoff / archi
7 matches
Mail list logo
