We would characterize that, internally, as NKNTW - which is
“Not Known Not To Work”
as opposed to the very dreaded KNTW (“Known Not To Work”)
:-)
- Dave R. -
--
[email protected] Work: (919) 676-0847
Get your mainframe programming tools at http://www.dignus.com
> On Jan 5, 2016, at 3:58 PM, Abe Kornelis <[email protected]> wrote:
>
> Dave, all,
>
> as z390 claims to produce MVS-compatible object deck output, that should
> not be a problem, then.
> Thanks for your quick answer!
>
> Kind regards & best wishes for 2016 to all of you!
> Abe
> ===
>
>
> Op 5-1-2016 om 21:52 schreef Dave Rivers:
>> Hi Abe,
>>
>> Sure! As long as it’s standard OBJ, GOFF or XOBJ object format it can be
>> input to our linker (and, for that matter, IBM’s binder.)
>>
>> - Dave R. -
>>
>>> On Jan 5, 2016, at 3:45 PM, Abe Kornelis <[email protected]> wrote:
>>>
>>> Martin, all,
>>>
>>> As I read it, you could even use z390 (supported on any Java platform)
>>> to create an object deck, then pass that as input to Dave's binder/linker.
>>>
>>> Am I right, Dave?
>>>
>>> Abe Kornelis
>>> z390 support team.
>>> =================
>>>
>>>
>>> Op 5-1-2016 om 17:49 schreef [email protected]:
>>>> Dave,
>>>>
>>>> let me see if i have this right-
>>>>
>>>> one can use the HLASM on z/OS (it's there anyway) and
>>>>
>>>> then use your "binder/linker" to produce stuff that can then be
>>>> processed by LNKEDT in z/VSE
>>>>
>>>> (I omitted the obvious step of running binder in z/OS to produce a
>>>> loadable module)
>>>>
>
