Hi list,
Wilbur source is not that "trashed".
After uploading it to USS I can access the code in a perfectly readable way
using ISPF Edit :
EDIT /u/sys56/WYLORV/Mainframe/GG.PUB/WINGS.COMMANDS Columns 00001 00
Command ===> Scroll ===> C
****** ***************************** Top of Data **************************
000001 ;
000002 ; Wings - ALLOCATE command
000003 ;
000004 xproc () begin
000005
000006 declare number x.pathno
000007 declare string open_str
000008 declare string open_opt
000009 declare string wing_path
000010 declare string msg xmsg pmsg
000011 declare string rc cr
000012 declare boolean debug
000013 cr = SHEX('0D') ; CR CHARACTER
000014
000015
000016 ;***debug: set true
000017 debug=false
I use ISPF 3.17 to access the directory. Edit the member on the displayed list.
Just that you must specify ASCII on the Edit Entry panel:
Data Encoding
1 1. ASCII
2. UTF-8
Furthermore you can use CUT and PASTE to copy it to a regular PDS.
Ciao,
--------------------------------------------------
Raphael Dal Pos / z/OS Support
Generali Shared Services S.c.a.r.l.
GSS\CIN-MF (Central Infrastructure Mainframe)
11-17, Avenue François Mitterrand
93200 Saint Denis / France
Wilo W 03 B1 029C
raphael.dal...@generali.com +(33)1-58-38-59-67
or mobile +(33)6.24.33.20.87
--------------------------------------------------
"MVS: Guilty, until proven innocent !!" RDP 2009
-----Message d'origine-----
De : IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] De la part
de Tony Harminc
Envoyé : jeudi 9 juillet 2020 01:33
À : IBM-MAIN@LISTSERV.UA.EDU
Objet : Re: SuperWylbur Users
On Wed, 8 Jul 2020 at 14:38, Farley, Peter x23353
<peter.far...@broadridge.com> wrote:
>
> Do you know of a specific program or macro in the package that exhibits this
> failure? Or have a link to any public discussion of the issue that describes
> the mis-translations?
>
> I DL'd the tgz file directly from Stanford and browsed a few sources at
> random, but I didn't see any "weird" characters. One of the mail-related
> scripts I reviewed seemed to have legitimate square bracket pairs, so maybe
> it isn't that particular issue?
I did much the same, and noticed that in the listing files there seems
to have been some post processing done to (among other things)
generate text boxes For example, in
Mainframe\GS.MIL\MILTEN.SOURCE\MSVC there is a line starting with *box
which in the matching listing Assemblies\Milten\MIL#MSVC.txt generates
a box made mostly of X'FE' for the horizontal lines, 9F for the
vertical, and the four corners are BF, DC, BE, and BB. This is neither
ASCII nor EBCDIC in any dialect I recognize, but all the box
characters have been uniquely translated, so that may well also be
true for any unusual characters in the actual source lines.
I doubt that the long-standing claim that the Wylbur source is trashed
is completely invented, but things certainly *look* salvageable at
first glance.
Tony H.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
