Yes this is the most right thing i needed
Here is the code i used to confide myself:
V$FUNCTION = 'TEST'
APP.NAME = 'ST.RBTTCO.ID.TYPES'
Y.N.COMPILED = 0
CALL CHECK.ROUTINE.EXIST(APP.NAME,Y.N.COMPILED,RET.INFO)
IF Y.N.COMPILED <> 0 THEN
PRINT 'APPLICATION COMPILED'
CALL @APP.NAME
END ELSE
PRINT 'APPLICATION IS NOT COMPILED'
END
This will be build in a loop and will not have to observe weather the main
program will fail for some routine or so.
Thanks VK
On Tue, Aug 4, 2009 at 8:52 AM, VK <[email protected]> wrote:
>
> Hi,
> firstly you can call any T24 app with prior assigment of V$FUNCTION
> var.
> E.g.:
> V$FUNCTION = 'Anything longer than 1 byte'
> CALL ACCOUNT
>
> Then you have F, N, T arrays etc populated.
>
> Secondly there's a T24 API function called CHECK.ROUTINE.EXIST. You
> can find its description in "Programming Standards.pdf"
>
> VK
>
> On Aug 3, 10:25 pm, Igor Micev <[email protected]> wrote:
> > Hi,
> > ST.RBTTCO.ID.TYPES is T24's application, I checked that there is no VOC
> file
> > for it.
> > I had problems only for that application, and just pressed C.
> >
> > I just eliminated that application from the list and the processing went
> > without problems.
> >
> > Thanks
> >
> >
> >
> > On Mon, Aug 3, 2009 at 7:14 PM, Jim Idle <[email protected]> wrote:
> >
> > > lwlodar wrote:
> > > > To do this kind of checking right, in good style, there is no other
> > > > option, than just write C function (as Jim said).
> > > > Still, you can do this in bad style - simply use EXECUTE and call
> > > > jshow, as long as you are doing only jBASIC development,
> > > > this should be enough (going further and using C/C++ this would be
> not
> > > > enrough),
> >
> > > > But I assume - you are talking about jBASIC only
> >
> > > > At the end - again, Jim is right - this is not the way - fix your
> > > > application - so there are no calls to non-existing routines,
> >
> > > Actually I suppose that if you are willing to use BASIC and CATALOG (or
> > > the T24 equivalents) then you should find an entry in the MD or VOC
> file
> > > that is named after the subroutine. You could therefore read the VOC
> > > file, determine that the entry looks correct and if it does then call
> > > the subroutine, otherwise do not. However, this does not guarantee
> > > correctness here and the issue s still that your design is not correct
> -
> > > you should have some other way to determine what subroutines are
> present
> > > and should be called according to some configuration. One of the
> reasons
> > > is that if the subroutines are not there and should be, you will
> > > silently ignore the issue. Stand back and look at your design and what
> > > you are really trying to achieve.
> >
> > > Jim
> >
> > --
> > Igor Micev
>
> >
>
--
Igor Micev
--~--~---------~--~----~------------~-------~--~----~
Please read the posting guidelines at:
http://groups.google.com/group/jBASE/web/Posting%20Guidelines
IMPORTANT: Type T24: at the start of the subject line for questions specific to
Globus/T24
To post, send email to [email protected]
To unsubscribe, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
-~----------~----~----~----~------~----~------~--~---
