IEB1135I
Paul Gilmartin
doesn't show it.
But doc won't help me; I was just probing to see how new
it is. What's bugging me is that at z/OS 1.10 the text
contains 12 NULs. At 1.7, either IEB1135I wasn't issued
or it contained no NULs.
Why is this a problem? I'm filtering SYSPRINT through
a sed(1) script, and z/OS's sed is hostile to NULs.
Is nonprintable characters in utility messages APARable?
What's a good way to get rid of NULs in the meantime?
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to list...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Lizette Koehler
If you are seeing NULS then I would open an ETR and get IBM to make them
Spaces.
Lizette
Paul Gilmartin
>I went into IBMLINK and it looks like it came in 1994
>
So how long is it supposed to take a message to diffuse from
IBMLink into M&C? Or is it one of those self-explanatory
messages that so delight this group?
>If you are seeing NULS then I would open an ETR and get IBM to make them
>Spaces.
>
Good idea. They've fixed one of these before. (In HLASM, IIRC.)
Hmmm. Obtain line buffer. XC to clear. Start stuffing fields.
And who were all these people ranting in the past week that one
should validate one's input? And why was I not paying attention?
Thanks for the research,
gil
Paul Gilmartin
>I went into IBMLINK and it looks like it came in 1994
>
I see the NULs at z/OS 1.10. I found a SYSPRINT from 1.7.
In that release, field contains the OS release. At 1.10,
it contains NULs. Looks very like a bug.
>If you are seeing NULS then I would open an ETR and get IBM to make them
>Spaces.
Thanks again,
Lizette Koehler
<vbg> there were only spaces. For what good assembler programmer would
allow x'00' instead of x'40' for spaces. ;-D
Lizette
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-...@bama.ua.edu] On
Behalf Of
> Paul Gilmartin
Paul Gilmartin
>Oh, I am certain that IBM checked it out completely before and made sure
><vbg> there were only spaces. For what good assembler programmer would
>allow x'00' instead of x'40' for spaces. ;-D
>
>> -----Original Message-----
>> From: IBM Mainframe Discussion List [mailto:IBM-...@bama.ua.edu] On Behalf Of
>> Paul Gilmartin
>> Sent: Friday, November 06, 2009 7:10 PM
>>
>> And who were all these people ranting in the past week that one
>> should validate one's input? And why was I not paying attention?
>>
Acutually, I was commenting on my own position in a recent prolonged
thread.
Thanks for the pointer to OY58953. SIS shows that they have considerable
trouble getting IEB1135I right -- most recently OA27718.
Sample output as attached to PMR Record 69695,033,000:
-----------------------------------------------------------------------------------------------------------------------------------
SDSF OUTPUT DISPLAY V940431X JOB03623 DSID 105 LINE 2 COLUMNS 02- 133
COMMAND INPUT ===> SCROLL ===> CSR
---+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0----+----1----+----2----+----3---
IEB1135I IEBCOPY FMID HDZ1A10 SERVICE LEVEL NONE DATED 20080414 DFP 3,3,2 1 HBB7750 CPU 2066
CCCFFFFC4CCCCDDE44CDCC4CCEFCFF44ECDECCC4DCECD4DDDC44444CCECC4FFFFFFFF4CCD4444F6F6F4F400000000000044444CCCFFFF44CDE4FFFF4444444444444
952113590952367800649408491110002595935035553056550000041354020080414046700003B3B201000000000000000000822775000374020660000000000000
----------------------------------------------------------------------------------------------------------------------------------
Thanks again for your assistance,
gil
McKown, John
> From: IBM Mainframe Discussion List
> [mailto:IBM-...@bama.ua.edu] On Behalf Of Paul Gilmartin
> doesn't show it.
>
> But doc won't help me; I was just probing to see how new
> it is. What's bugging me is that at z/OS 1.10 the text
> contains 12 NULs. At 1.7, either IEB1135I wasn't issued
> or it contained no NULs.
>
> Why is this a problem? I'm filtering SYSPRINT through
> a sed(1) script, and z/OS's sed is hostile to NULs.
>
> Is nonprintable characters in utility messages APARable?
>
> What's a good way to get rid of NULs in the meantime?
>
> -- gil
cat file.with.nulls | tr -d '\000' | command.
--
John McKown
Systems Engineer IV
IT
Administrative Services Group
HealthMarkets(r)
9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone * (817)-961-6183 cell
john....@healthmarkets.com * www.HealthMarkets.com
Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM
Chase, John
> > From: IBM Mainframe Discussion List
> > On Behalf Of Paul Gilmartin
> >
> > doesn't show it.
Neither does QuickRef, but in response to a QuickRef search for IEB1135I
I got this:
======== Begin paste ==============
********************* Text Below Copyright (c) 2009, IBM
*********************
IEB1134D - IEB1137D diagnostic_text
Explanation: The following messages contain diagnostic information for
you to supply to IBM when requesting service:
o IEB1134D
o IEB1135D
o IEB1136D
o IEB1137D
======== End paste ===================
Nothing more, and nothing specifically about IEB1135I.
-jc-
Paul Gilmartin
>>
>> What's a good way to get rid of NULs in the meantime?
>>
>
truly superfluous.
Lizette sent me privately OY58953, which says:
--- MSGIEB1135I ----------------------------------------------
IEB1135I <mod> FMID <fmid> SERVICE LEVEL <ptf> DATED <date>
<df_product> MVS <cvtprod> CPU <cvtmdl>
EXPLANATION: Please supply ALL info when requesting service.
It's what I put in the APAR. Will they reject the ETR because
one of the fields they require is null?
Is OY58953 the correct place to keep the doc of this message?
Nowadays, if LOOKAT doesn't find it, I deem it missing.
Thanks,
gil
Paul Gilmartin
>Oh, I am certain that IBM checked it out completely before and made sure
><vbg> there were only spaces. For what good assembler programmer would
>allow x'00' instead of x'40' for spaces. ;-D
>
IBM says, known problem, repaired by OA27718. We're ordering.
ERROR DESCRIPTION:
IEBCOPY messages: MSGIEB1135I has incorrect FMID.
MSGIEB1017W has extraneous information.
Doesn't say a lot about x'00'. Who woulda guessed it. IBM
found because they couldn't recreate at their service level.