SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Information Architects (IARC): E-Commerce & EIP

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Done, gone. who wrote (2008)8/20/1997 3:16:00 PM
From: TEDennis   of 10786
 
Czech: My point (rather obscure, I admit) was that it doesn't really matter how much source code you have if you're using one of the Source Library Manager packages that run on the mainframe. If your Y2K solution executes on a PC or UNIX machine, you can't get to your source code to scan or repair it. Minor detail, eh?

Instead of using "COPY" to bring common source code (like data descriptions or code snippets) into the compile, the Library Managers use their own rendition .... ++INC for Panvalet, and -INC for Librarian, and there are a couple of other, less prevalent, managers. The scanners must be able to interpret those statements and perform the relevant copying activity. Note that some of the older compilers didn't allow nested COPY statements, but the Library Managers do. So, you can't just edit your source code to change ++INC to COPY and get the same results as you did with the Library Manager.

There are lots of issues surrounding these environmental concerns. I would much rather rely on a mainframe oriented tool where the code resides and is executed than a PC/UNIX tool. Spoken as a 100% true-blue mainframe bigot, by the way.

TED
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext