×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hi Folks,
I have helped Jonathan solve the problem off-list.
For those that are curious, he was missing some of the characters at the
beginning of the source member. On my system, the HSSF_H member begins
with the following line of code (the slash is in column 7):
/if not defined(HSSF_H)
For some reason, however, Jonathan's copy started as follows (at least,
this is what he tells me):
not defined(HSSF_H)
This causes the "n" to be in column 6 (the form-type column) which in
turned caused all of the other errors. It may be that the 5 leading
blanks were stripped from that line in his source member (a common
copy/paste error) or that his member was somehow altered... hard to
know... but the problem is solved now.
Jonathan A Albrecht wrote:
002800 070511
002900 /copy smmsrcile,hssf_h 070604
*RNF0257 30 1000100+ Form-Type entry for main procedure not valid
or out of HFAPGMSM/SMMSRCILE(HSSF_H)
sequence.
LINES EXCLUDED: 0
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
