I have been asked to modify a medium sized IND control
file in order to upgrade a system to Y2K compliance. The
specifications call for testing a specific file on the old data
diskette and replacing it with a new version. In the course
of making the changes, I have had a problem! Rather than
post the complete IND control file, I have retained the
statements which are causing the problem. And they have
been modified so as to be generalized.
Please be aware that while these statements serve no useful
purpose by themselves, all but their essence was removed
so as to produce this example in which the problem still
appears. Most are from the original control file and a few
are present due to the new specifications. So PLEASE
don't just respond that the control files shown serve no
useful purpose - 99% is missing and only the part which
causes the problem has been retained. Someone taking
a quick look at the problem might dismiss it as useless.
I have 2 questions:
(a) Is my understanding of IND incorrect and am I
using IND in an incorrect manner?
(b) Is there a bug in IND which is causing the problem?
I have attached 2 files. The first is the minimum which
causes the problem. The second provides a control
test situation which does seem to work at first, but
not under the conditions which are present in the
"minimum" test file.
Anyone out there who is still working with RT-11?
Sincerely yours,
Jerome Fine
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Mintst.cmd
Type: application/x-unknown-content-type-cmd_auto_file
Size: 512 bytes
Desc: not available
Url :
http://www.classiccmp.org/pipermail/cctalk/attachments/19981218/c7e2e69f/Mintst.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Indtst.cmd
Type: application/x-unknown-content-type-cmd_auto_file
Size: 512 bytes
Desc: not available
Url :
http://www.classiccmp.org/pipermail/cctalk/attachments/19981218/c7e2e69f/Indtst.bin
Received on Fri Dec 18 1998 - 09:20:27 GMT