Note also that the assembly listing you mentioned has a step that
post-processes the ASM SYSPRINT output:
15 //EDIT EXEC PGM=ASMEDIT,TIME=2,REGION=4000K,
// PARM='STMT'
16 //STEPLIB DD DSN=WYL.GG.SYS.LINKLIB,DISP=SHR
17 //ASMOUT DD DSN=&PRINT,DISP=(OLD,DELETE)
18 //SYSPRINT DD SYSOUT=A
That seems to be a common last step in the assemblies I reviewed.
I did not see any ASMEDIT routine anywhere in that package, but if that is all
it does it would probably not be hard to duplicate the function. I'll bet
those "box draw" characters are specific to whatever laser or networked printer
setup they had at the time.
The unfortunate choice to suppress macro output in the assembly listings would
undoubtedly make it harder to fully duplicate and verify new assemblies, and
certainly any object-code-only files that may have been supplied in the various
directories would almost certainly have been irretrievably trashed. If
operation of the product depends on any OCO subroutines in the package, then
that certainly would be *the* serious block to implementation, with any chance
of recovery not very probable.
I certainly had no intention to demean Gerhard, with whom I corresponded on
other email lists. A gentleman and an expert in multiple disciplines who
freely shared his expertise. If he failed after intensive effort, I wouldn’t
presume to be his better.
Peter
-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of
Tony Harminc
Sent: Wednesday, July 8, 2020 7:33 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: 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.
--
This message and any attachments are intended only for the use of the addressee
and may contain information that is privileged and confidential. If the reader
of the message is not the intended recipient or an authorized representative of
the intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this communication
in error, please notify us immediately by e-mail and delete the message and any
attachments from your system.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
