Great minds must think alike!!!!

        After seeing this recently in a thread here, I decided to download B2H 
and try it.

        I initially received the exact same error you have listed below. To get 
past this issue, I changed the default MVS Dataset Allocations (search on 
MVSAlloc) to use an LRECL of 2048. At approximately line 467,  I have the 
following:

        MVSalloc.          ='DSORG(PS) LRECL(2048) RECFM(V) TRACKS    
SPACE(5,5) RELEASE'

        This change did get me past the B2H317 error and I did ultimately 
produce an html file. However, some of the boxes did NOT format 
correctly........

        I am still tinkering with it............

        Good Luck
        Hth
        Tony 


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Dyck, Lionel B. (TRA)
Sent: Friday, July 28, 2017 7:36 AM
To: [email protected]
Subject: Friday Fun: hcd charts to htm via b2h issue

Has anyone successfully used b2h for an iodf chart on z/OS?

I've uploaded b2h and created both lcu and switch charts and when I run them I 
get these errors on z/OS

|B2H455 WARNING:   :xmp scale='.6  ' :ih1.control unit, by # :i2.1000
|B2H455 WARNING:   (in line 1789 of T311LBD.IODF1.REPORT)
|B2H317 ERROR:   RC=1 output record truncated while writing to DD=B2H00007 
DSN='T311LBD.B0029556.$TMP0391' Record='  &nbs
p;  |           |        &
nbsp;  |           |       &nbs
p;   |           |       &
nbsp;   |           |      &nbs
p;   |           |       &
nbsp;   |           |      &nbs
p;    |           |      &
nbsp;    |           |'
|B2H107 Info:    Highest RC=8

When I run it under oorexx under windows the lcu chart looks great but the 
switch charts has these anomalies:

       0   1   2                                           0   1   3
    
&bx0220.&bx0202.00&bx0202.&bx0202.02&bx0202.&bx0202.04&bx0202.&bx0202.06&bx0202.&bx0202.07&bx0202.&bx0202.08&bx0202.&bx0202.09&bx0202.&bx0202.0A&bx0202.&bx0202.0B&bx0202.&bx0202.0C&bx0202.&bx0202.0D&bx0202.&bx0202.0E&bx0202.&bx0202.0F&bx0202.&bx0202.10&bx0202.&bx0202.12&bx0202.&bx0202.14&bx0202.&bx0202.16&bx0202.&bx0202.17&bx0202.&bx0202.18&bx0202.&bx0202.19&bx0202.&bx0202.1A&bx0202.&bx0202.1B&bx0202.&bx0202.1C&bx0202.&bx0202.1D&bx0202.&bx0202.1E&bx0202.&bx0202.1F&bx0202.&bx0202.20&bx0202.&bx0202.21&bx0202.&bx0202.22&bx0202.&bx0202.23&bx0202.&bx0202.24&bx0202.&bx0202.25&bx0202.&bx0202.26&bx0202.&bx0202.27&bx0202.&bx0202.28&bx0202.&bx0202.29&bx0202.&bx0202.2A&bx0202.&bx0202.2B&bx0202.&bx0202.2C&bx0202.&bx0202.2D&bx0202.&bx0202.2E&bx0202.&bx0202.2F&bx0202.&bx0202.30&bx0202.&bx0202.31&bx0202.&bx0202.32&bx0202.&bx0202.33&bx0202.&bx0202.34&bx0202.&bx0202.&bx0202.&bx0202.&bx0202.&bx0202.&bx0202.&bx0202.
    &bx2020.
    &bx2020.

Any advice/suggestions?

I can't see spending the $$$$ that IBM is asking for DCF as this is the only 
reason we would use it.

Thanks in advance

--------------------------------------------------------------------------
Lionel B. Dyck
Mainframe Systems Programmer - TRA

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to