comp.databases.pick Google Group

Re: USER-COLDSTART

pierre.walthe...@gmail.com (Pierre) — Sat, 11 Nov 2009 08:34:38 UT

To be able to execute a program in the USER-COLDSTART, you should give
the complet way to find it (ACCOUNT,PROGRAMFILE, PROGRAM). It the
same for the OPEN instruction, then the program will work everywhere
in the database.
Pierre

Re: USER-COLDSTART

ud.u2....@gmail.com (Colin) — Fri, 11 Nov 2009 19:55:28 UT

It's been a long time since I've worked with AIX and D3 but I'm siding
with Tony's idea on permissions.
Either that or something silly like the program is not cataloged in
the DM account where the user-coldstart runs.
Things to try:
- have your program do something simple like CRT "running
WHAT.SERVER.AM.I"

Re: ftp problem

mikewood...@email.com (Mike Wooding) — Fri, 11 Nov 2009 17:58:49 UT

In your shoes, I'd check basic network connectivity before going anywhere
near FTP.
So, apologies if any / all of what follows seems obvious, but as you say
both AIX servers are identical and that you can FTP between the two AIX
boxes, I'd look first and foremost at the Windows box.
Do both interfaces show up when you perform a "route print" (from a "CMD"

Re: USER-COLDSTART

address.is.in.po...@removethis.com.invalid (Tony Gravagno) — Fri, 11 Nov 2009 17:34:41 UT

I don't know specifically why your program isn't running but there
isn't enough info yet to come to any conclusions. Here's a little
background on what's happening in there, and some further ideas.
System-coldstart is a dm,md macro that does a bunch of stuff before it
comes down to a "coldstart" verb. "coldstart" is just another macro

Re: ftp problem

dan...@southwesttraders.com (dannyruckel) — Fri, 11 Nov 2009 16:49:38 UT

hey pierre,
the machines are on different subnets but both are seen and can be
pinged from the windows machine.
i never get a 220 response from the target machine so can't speak to
the user rights.
thanks again for taking the time to respond.
danny

Re: USER-COLDSTART

dan...@southwesttraders.com (dannyruckel) — Fri, 11 Nov 2009 16:42:20 UT

good a.m. pierre,
thanks for taking the time to respond.
i am keeping the proc but from within the proc call a basic program to
determine what server i am on (we have multiple here). depending on
which server USER-COLDSTART is executing, the routine starts printers/
phantoms.
when i use this routine in any proc other than USER-COLDSTART it works

Re: USER-COLDSTART

dan...@southwesttraders.com (dannyruckel) — Fri, 11 Nov 2009 16:39:27 UT

thanks for the reply ross!
i have changed all the 'P's to 'PW's and was able to determine the
point of failure. there is a basic routine that i have written
specifically for determining what server i am on during startup. once
i determine what server i am on i can decide whether i should start
printers/phantoms. it was for this reason i converted USER-COLDSTART

Re: USER-COLDSTART

dan...@southwesttraders.com (dannyruckel) — Fri, 11 Nov 2009 16:34:05 UT

kevin,
thanks for the reply. what i am attempting to do is, through the
course of the USER-COLDSTART routine, determine the hostname of the
AIX server i am on. I am running the same USER-COLDSTART routine on
multiple servers. if the hostname of a server is, say "Kevin", i want
to start printers and assign phantom jobs to phantom processes. if

Re: ftp problem

pierre.walthe...@gmail.com (Pierre) — Thu, 11 Nov 2009 10:10:53 UT

Hi Danny,
First question but it could be important, are the both AIX on the same
IP adress mask with the windows machine ?
Do you see the two AIX serveur with the windows machine ?
Other possibility : Have the ftp user the same right on both AIX ?
Pierre

Re: USER-COLDSTART

pierre.walthe...@gmail.com (Pierre) — Thu, 11 Nov 2009 10:03:04 UT

Danny,
I'm like Ross : Why do you don't stay in PROC format ?
It's what we do and it's working fine and then you will be sure that's
will be work in both case.
Pierre

Re: USER-COLDSTART

ro...@stamina.com.au (Ross Ferris) — Thu, 11 Nov 2009 00:44:08 UT

In the first instance I'd change all of the P's to PW's in the PROC -
reboot to re-execute the coldstart proc, and then at least you will
have visual feedback of WHERE things are going off the rails
I also question the need to convert to a PROC --> why not refer to
"your proc" from the user-coldstart macro?

Re: USER-COLDSTART

kpow...@gmail.com (Kevin Powick) — Thu, 11 Nov 2009 00:03:27 UT

Not really enough information about what exactly isn't working in the
proc, but some things do behave differently during start-up. For
instance, running a job on a phantom (z) does not require the account
password input as one of the stacked input arguments when run from a
proc. So, if you build such a proc that works at TCL, it will fail if

Pick Programmers in Brisbane Australia

m...@qedgroup.com (QED Group) — Wed, 11 Nov 2009 23:06:14 UT

Hi, We have a piece of proprietary software written in PICK. It is
quite solid but from time to time it requires work on file corruption
and other minor updates. Support has wanned away and we are in need
of accessing programmers for ad hoc administration. Can anyone point
me to local programmers capable of working in PICK software. Many

USER-COLDSTART

dan...@southwesttraders.com (dannyruckel) — Wed, 11 Nov 2009 20:12:43 UT

we are currently using D3 7.4.2.RS on AIX 5.3 TL10.
we had a USER-COLDSTART defined as a macro (attribute 1 = 'n') but
i've necessarily changed it to a proc (attribute 1 = 'pq') when i
test the logic of this USER-COLDSTART outside the context of starting
D3 the proc executes as expected, however, in the context of starting

ftp problem

dan...@southwesttraders.com (dannyruckel) — Wed, 11 Nov 2009 20:04:01 UT

i am trying to put a windows machine, dual nics, between two AIX
servers. it seems i can ftp from the windows machine to one of the
AIX servers, but not the other.
/etc/inetd.conf is identical on both AIX servers and i can ftp between
the 2 AIX servers.
any ideas why i can't ftp from the windows machine to both AIX