×
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.
Sorry if I wasn't clear Rob. I used SEP's to determine the below when
calling the proc from ops nav. That's why this is so weird I have watched
the call to write and the call to close "work" in WDSC yet the file is empty
when I look inside it.
"When I debug the stored procedure call, the call the write , returns the
number of bytes written that I expect and the call to close does not
return
an error. There is nothing in the job log."
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: 23 June 2010 13:29
To: Midrange Systems Technical Discussion
Subject: Re: External Stored Procedure writing to IFS Stream file
There are these things called "Service Entry Points" or SEP. Basically
you can, if you follow the instructions carefully, start a debug session
on a program. But with SEP's you can have it start debugging in your
session (or WDSC aka RDi, aka RDP) from whatever job calls that program.
I recommend giving that a try.
As an Amazon Associate we earn from qualifying purchases.
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.