Thanks, Brian. I will tinker with that. I knew that PERFORM did something different and I did try that. But I didn't know about the In and Out syntax on execute.
SJ -----Original Message----- From: Brian Leach [mailto:br...@brianleach.co.uk] Sent: Thursday, September 27, 2012 4:22 AM To: sjos...@sjplus.com; 'U2 Users List' Subject: RE: [U2] Universe and data-stacking Susan Execute runs differently in different flavors. EXECUTE creates a new environment. That environment doesn't inherit all the baggage of the calling environment unless you redirect input, output, select lists etc. to and from the EXECUTE statement, e.g. EXECUTE Cmd, IN. < stacked_data, OUT. > output, SELECT. < incoming_select, SELECT. > outgoing_select In INFORMATION flavor EXECUTE is equivalent to PERFORM and doesn't create a new environment, unless you explicitly add redirect options. You can change this by using the $OPTIONS EXEC.EQ.PERF in your program which means 'compile Execute as Perform' or use PERFORM. Brian -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Susan Joslyn Sent: 27 September 2012 03:46 To: 'Kevin King'; 'U2 Users List' Subject: Re: [U2] Universe and data-stacking I'll try that, thanks! Still a mystery why it works differently in different universe accounts on the same server though. From: precisonl...@gmail.com [mailto:precisonl...@gmail.com] On Behalf Of Kevin King Sent: Wednesday, September 26, 2012 10:29 PM To: sjos...@sjplus.com; U2 Users List Subject: Re: [U2] Universe and data-stacking Rather than data stacking, can you do this: EXECUTE 'SB.LOGIN user,password,terminal' Where the lower case stuff is the appropriate user, password, and term type? On Wed, Sep 26, 2012 at 8:23 PM, Susan Joslyn <sjos...@sjplus.com> wrote: Hi geniuses! I know that in Unidata there is a udt options flag that allows data-stacking to work. I can't find anything similar in Universe. But even if I could, my problem seems to run a little deeper than that. I can write a test program that data stacks two pieces of info into another program that has two input commands. No problem, that works. But if I try to CHAIN or EXECUTE SB.LOGIN datastacking the user ID and password it fails. But get this - it succeeds in some of the accounts (universe directory accounts) but fails in others. Is there something about the accounts, the flavor, some setting that would prevent a datastack from making it -- maybe because it is a chained command? I tried it with EXECUTE, no difference. Anyone run into something like this? Anyone who is an SB+ user might suggest that I use the AUTOLOGIN option, but that doesn't change the behavior at all. It still makes me login, still won't take the data stack. I am not well-versed at administrative commands that might tell me things about the account settings and flavor and tunable parameters - so if there is something obvious I could look at, don't assume that I know it. Any and all help, as always, greatly appreciated! Susan _______________________________________________ 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
