It seems to me that I remember something along the lines of, if the subroutine code lives in the same file as the calling program code, then you don't actually have to CATALOG the subroutine in order for the calling program to be able to find it and run it.
-----Original Message----- From: Israel, John R. <johnisr...@daytonsuperior.com> To: U2 Users List <u2-users@listserver.u2ug.org> Sent: Wed, Mar 20, 2013 12:12 pm Subject: Re: [U2] History.. Also, Once a program is cataloged, you no longer need to type the "RUN filename programname". You can just type the programname. Note that if the program is a subroutine AND it has arguments, you cannot run this from TCL. It will blow up right away. No harm, but no execution either. You also have to catalog a program in order to CALL it by another program. Be sure to understand the impact of cataloging globally (the default) vs. locally. We catalog everything locally on our box which simply builds a VOC pointer to the object code. This means that once it is cataloged once, we never need to catalog it again, but other accounts cannot see it w/o being cataloged in those other accounts too. Globally cataloged programs are available to anyone on the box (but can lead to confusion between different account w/ different versions of the same program). Both global and local have their advantages and disadvantages. JRI -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Allen Egerton Sent: Wednesday, March 20, 2013 2:25 PM To: U2 Users List Subject: Re: [U2] History.. John answered your sentence stack commands, so I'll take a shot at how to execute a program. Typically programs are stored in type 1 files, aka directories or folders, (terminology usually depends upon base operating system, *ix or windows). There's a corresponding file containing the object code. To execute the program, you would typically enter RUN filename programname at the command prompt. Then, there's cataloged code which is a method of storing object code so that it can be referenced by multiple users, (unless it's cataloged "locally"). You can also execute a program directly from its native host without entering UniData if you know where the binary executable lives. The last three are included only for some semblance of completeness, I believe that the answer you're looking for right now is paragraphs two and three. On 3/19/2013 11:17 AM, Sathya wrote: > Hi all,.. > > I'm pretty new to Unidata. just wanted to know the command for listing > the history of commands and how to select nth number of command. > > Also how to execute a unidata program. > > I know my questions will be very simple. But as I'm entirely new to > this, unable to find that anywhere :-( > > TIA, > Sathya V. > > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users > _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
