Could be hardware, could be an attack. Guess start with packet traces. We had a couple of lengthy runs had to put on 'milking machines' before the cable could be replaced. In a message dated 9/15/2014 1:52:56 P.M. Central Daylight Time, [email protected] writes:
It was an assembler macro, so “MACRO blah”, but we do this a lot and the same file re-uploaded with the same options worked. But yeah, maybe something dropped a byte and that led it to misread…only why did it (a) work at all and (b) put the directive in the file, replacing the MACRO line? Mystery! ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
