 SOSUPD for UNIX
#28934
23 May 07 12:04 AM
|
Joined: Jun 2001
Posts: 11,645
Jack McGregor
OP
Member
|
|
OP
Member
Joined: Jun 2001
Posts: 11,645 |
SOSUPD.RUN 2.1(105) now works under A-Shell/UNIX, which should make it a lot easier to update the SOSLIB under AIX and LINUX. (It is no longer necessary to first run SOSUPD under A-Shell/Windows, then FTP all the files over to A-Shell/UNIX.) As with ASHUPD and ATEUPD, there are probably many improvements needed, but since the SOSLIB is a developer toolkit anyway, the risks associated with any bugs are fairly trivial. Note that if you've never installed the SOSLIB under A-Shell/UNIX, just log to dsk0:[901,2] (create the PPN if necessary), then download the copy of SOSUPD.RUN from the link at the top of this message into that PPN, then RUN SOSUPD. It's a bit slow the first time, as there will be hundreds of individual files to be downloaded. The real payoff is in subsequent updates where it will very quickly identify and download just those files that need to be updated. Here's a screen shot of a sample run. (I had deleted the [907,10] directory to test re-creating it.): .LOG 901,2
.RUN SOSUPD
SOSLIB Update
Checking for SOSLIB updates...
Creating PPN: /vm/source50/dsk0/907010
New: fnalloc.bsi[907,010]
New: fndec2hex.bsi[907,010]
New: fnexplode.bsi[907,010]
New: fnextch.bsi[907,010]
New: fngcd.bsi[907,010]
New: fnhex2dec.bsi[907,010]
New: fnhostex.bsi[907,010]
New: fnhttpget.bsi[907,010]
New: fnminmax.bsi[907,010]
New: fnprogver.bsi[907,010]
New: fnsprintf.bsi[907,010]
New: start.cmd[907,010]
New: test.dat[907,010]
Operation complete; 13 files updated.
See OPR:SOSUPD.TRC and OPR:SOSUPD.LOG for trace/log details
. As with ASHUPD under UNIX, it creates both a LOG and a debug/trace (TRC) file in the OPR account, and backs up any individual files that are being updated. Here's what the SOSUPD.LOG for the above update looks like: ------------------------------
22-May-07 22:58:11 Checking for SOSLIB updates...
22-May-07 22:58:11 Creating PPN: /vm/source50/dsk0/907010
22-May-07 22:58:11 Starting update...
22-May-07 22:58:12 New: fnalloc.bsi[907,010]
22-May-07 22:58:14 New: fndec2hex.bsi[907,010]
22-May-07 22:58:15 New: fnexplode.bsi[907,010]
22-May-07 22:58:16 New: fnextch.bsi[907,010]
22-May-07 22:58:17 New: fngcd.bsi[907,010]
22-May-07 22:58:18 New: fnhex2dec.bsi[907,010]
22-May-07 22:58:18 New: fnhostex.bsi[907,010]
22-May-07 22:58:18 New: fnhttpget.bsi[907,010]
22-May-07 22:58:20 New: fnminmax.bsi[907,010]
22-May-07 22:58:21 New: fnprogver.bsi[907,010]
22-May-07 22:58:21 New: fnsprintf.bsi[907,010]
22-May-07 22:58:22 New: start.cmd[907,010]
22-May-07 22:58:23 New: test.dat[907,010]
|
|
|
|
Re: SOSUPD for UNIX
#28936
23 May 07 08:47 AM
|
|
Anonymous
Unregistered
|
|
Anonymous
Unregistered
|
The new version is in the SOSUPD update. You can update A-Shell Windows' SOSUPD and then copy SOSUPD.RUN to the AIX machine. Then you can run the new version from AIX. I did something similar but ran from a Linux VM. Works great!
|
|
|
|
Re: SOSUPD for UNIX
#28937
23 May 07 09:11 AM
|
Joined: Sep 2003
Posts: 4,135
Steve - Caliq
Member
|
|
Member
Joined: Sep 2003
Posts: 4,135 |
Good thinking. (I never checked the Windows version, thinking it would be the same) All working as advertised. 
|
|
|
|
Re: SOSUPD for UNIX
#28938
23 May 07 09:13 AM
|
Joined: Jun 2001
Posts: 11,645
Jack McGregor
OP
Member
|
|
OP
Member
Joined: Jun 2001
Posts: 11,645 |
Good observations, both of you. I did mess up on the link (now fixed), but as you noted, you could get the updated SOSUPD from running the SOSUPD process under Windows first.
|
|
|
|
Re: SOSUPD for UNIX
#28939
28 May 07 09:39 PM
|
|
Anonymous
Unregistered
|
|
Anonymous
Unregistered
|
I've noticed that SOSUPD is updating every night from Linux but not from Windows. I looked at the log and found this: 24-May-07 21:23:19 Checking for SOSLIB updates...
24-May-07 21:23:19 Starting update...
24-May-07 21:23:19 Archived: sosupd.bas to sosupd.001
24-May-07 21:23:19 Updated: sosupd.bas[901,002]
24-May-07 21:23:20 Archived: sosupd.run 2.1(105) to sosupd.001
24-May-07 21:23:20 Updated: sosupd.run[901,002] 2.1(106)
24-May-07 21:23:21 Archived: fnprogver.bsi to fnprogver.001
24-May-07 21:23:21 Updated: fnprogver.bsi[907,010]
------------------------------
26-May-07 19:53:55 Checking for SOSLIB updates...
26-May-07 19:53:55 Starting update...
26-May-07 19:53:57 Archived: fnprogver.bsi to fnprogver.001
26-May-07 19:53:57 Updated: fnprogver.bsi[907,010]
------------------------------
26-May-07 19:54:02 Checking for SOSLIB updates...
26-May-07 19:54:02 Starting update...
26-May-07 19:54:04 Archived: fnprogver.bsi to fnprogver.001
26-May-07 19:54:04 Updated: fnprogver.bsi[907,010]
------------------------------
26-May-07 20:01:35 Checking for SOSLIB updates...
26-May-07 20:01:35 Starting update...
26-May-07 20:01:36 Archived: fnprogver.bsi to fnprogver.001
26-May-07 20:01:36 Updated: fnprogver.bsi[907,010]
------------------------------
28-May-07 22:47:44 Checking for SOSLIB updates...
28-May-07 22:47:45 Starting update...
28-May-07 22:47:46 Archived: fnprogver.bsi to fnprogver.001
28-May-07 22:47:46 Updated: fnprogver.bsi[907,010]
.dir/h/u [907,10]fnprogver
FNPROGVER BSI 4 105-406-726-047 21-May-07 21:40 DSK0:[907,10]
FNPROGVER 001 4 105-406-726-047 21-May-07 21:40
FNPROGVER 002 4 105-406-726-047 21-May-07 21:40
Total of 3 files in 12 blocks [907,10]FNPROGVER.BSI is always backed up and updated. The files are identical. I then checked the trace and found this: 24-May-07 21:23:19 Checking for SOSLIB updates...
24-May-07 21:23:19 Updating sosupd.bas: cur: 2007-05-22 22:40:0, 27627 bytes; new: 2007-05-23 22:32:44, 34533 bytes
24-May-07 21:23:19 Backing up sosupd.bas to sosupd.001
24-May-07 21:23:19 Hostex: unzip -o sosupd.zip >tskaaa.tmp 2>&1
24-May-07 21:23:19 Archive: sosupd.zip
24-May-07 21:23:19 inflating: sosupd.bas
24-May-07 21:23:19 Updating sosupd.run: cur: 2007-05-22 22:40:0, 16878 bytes; new: 2007-05-23 22:32:44, 19298 bytes
24-May-07 21:23:20 Backing up sosupd.run to sosupd.001
24-May-07 21:23:20 Hostex: unzip -o sosupd.zip >tskaaa.tmp 2>&1
24-May-07 21:23:20 Archive: sosupd.zip
24-May-07 21:23:20 inflating: sosupd.run
24-May-07 21:23:20 Updating fnprogver.bsi: cur: 2007-05-21 21:40:4, 1597 bytes; new: 2007-05-22 22:18:58, 1967 bytes
24-May-07 21:23:21 Backing up fnprogver.bsi to fnprogver.001
24-May-07 21:23:21 Hostex: unzip -o sosupd.zip >tskaaa.tmp 2>&1
24-May-07 21:23:21 Archive: sosupd.zip
24-May-07 21:23:21 inflating: fnprogver.bsi
------------------------------
26-May-07 19:53:55 Checking for SOSLIB updates...
26-May-07 19:53:55 Updating fnprogver.bsi: cur: 2007-05-21 21:40:4, 1597 bytes; new: 2007-05-22 22:18:58, 1967 bytes
26-May-07 19:53:57 Backing up fnprogver.bsi to fnprogver.001
26-May-07 19:53:57 Hostex: unzip -o sosupd.zip >tskaaa.tmp 2>&1
26-May-07 19:53:57 Archive: sosupd.zip
26-May-07 19:53:57 inflating: fnprogver.bsi
------------------------------
26-May-07 19:54:02 Checking for SOSLIB updates...
26-May-07 19:54:02 Updating fnprogver.bsi: cur: 2007-05-21 21:40:4, 1597 bytes; new: 2007-05-22 22:18:58, 1967 bytes
26-May-07 19:54:04 Backing up fnprogver.bsi to fnprogver.001
26-May-07 19:54:04 Hostex: unzip -o sosupd.zip >tskaaa.tmp 2>&1
26-May-07 19:54:04 Archive: sosupd.zip
26-May-07 19:54:04 inflating: fnprogver.bsi
------------------------------
26-May-07 20:01:35 Checking for SOSLIB updates...
26-May-07 20:01:35 Updating fnprogver.bsi: cur: 2007-05-21 21:40:4, 1597 bytes; new: 2007-05-22 22:18:58, 1967 bytes
26-May-07 20:01:36 Backing up fnprogver.bsi to fnprogver.001
26-May-07 20:01:36 Hostex: unzip -o sosupd.zip >tskaaa.tmp 2>&1
26-May-07 20:01:36 Archive: sosupd.zip
26-May-07 20:01:36 inflating: fnprogver.bsi
------------------------------
28-May-07 22:47:44 Checking for SOSLIB updates...
28-May-07 22:47:45 Updating fnprogver.bsi: cur: 2007-05-21 21:40:4, 1597 bytes; new: 2007-05-22 22:18:58, 1967 bytes
28-May-07 22:47:46 Backing up fnprogver.bsi to fnprogver.001
28-May-07 22:47:46 Hostex: unzip -o sosupd.zip >tskaaa.tmp 2>&1
28-May-07 22:47:46 Archive: sosupd.zip
28-May-07 22:47:46 inflating: fnprogver.bsi
.host ls -l /vm/miame/dsk0/907010/fnprogver.*
-rw-rw-rw- 1 root users 1597 2007-05-21 21:40 /vm/miame/dsk0/907010/fnprogver.001
-rw-rw-rw- 1 root users 1597 2007-05-21 21:40 /vm/miame/dsk0/907010/fnprogver.002
-rw-rw-rw- 1 root users 1597 2007-05-21 21:40 /vm/miame/dsk0/907010/fnprogver.bsi
.host ls -ld /vm/miame/dsk0/907010
drwxrwxrwx 2 root users 4096 2007-05-28 22:47 /vm/miame/dsk0/907010 I checked [907,10]TSKAAA.TMP and found what is shown in the trace above. I checked permissions in case there was an error that didn't get sent to the trace. As you can see, permissions weren't an issue so I checked the code to see if errors even went to the trace. They do, unless the user isn't using BASH, Korn, or similar shells (I use ksh93). The trace shows the standard error redirection any way. I don't know why FNPROGVER keeps updating in Linux. I have no idea why I ran SOSLIB 3 times in 8 minutes (and twice within seconds) on Saturday night.
|
|
|
|
Re: SOSUPD for UNIX
#28940
28 May 07 11:09 PM
|
|
Anonymous
Unregistered
|
|
Anonymous
Unregistered
|
The above repeatedly updating file is repeatedly updated on our home server. It's uname is $ uname -a
Linux xxx.xxxxxxx.xxx 2.4.20-8smp #1 SMP Thu Mar 13 17:45:54 EST 2003 i686 i686 i386 GNU/Linux
|
|
|
|
Re: SOSUPD for UNIX
#28941
29 May 07 09:41 AM
|
|
Anonymous
Unregistered
|
|
Anonymous
Unregistered
|
The latest SOSLIB run from Linux put up a newer version of ASHUPD.RUN [1.2(111)] than is available in SYS: [1.2(110)].
|
|
|
|
Re: SOSUPD for UNIX
#28942
29 May 07 10:08 AM
|
Joined: Jun 2001
Posts: 11,645
Jack McGregor
OP
Member
|
|
OP
Member
Joined: Jun 2001
Posts: 11,645 |
I'm going to try to get the various xxxUPD packages up to date and in-sync today. (Among other things, I'm going to remove ASHUPD.LIT from SOSUPD and on the next update, I'm going to have it check first for an update of itself to eliminate the need to update twice.)
On the problem with fnprogver.bsi being updated over and over again, I'm guessing that there was mismatch between the UpdateCenter's index file (which contains the date stamp info for all the files) and the actual file that I posted. I think it got straightened out in last night's update of the SOSLIB.
|
|
|
 Re: SOSUPD for UNIX
#28943
29 May 07 11:18 AM
|
|
Anonymous
Unregistered
|
|
Anonymous
Unregistered
|
I ran SOSUPD once this morning, which got some things and fnprogver. I guess this updated a copy of the index on my system because now fnprogver doesn't get updated when I run SOSUPD. Good plan taking ASHUPD out of SOSUPD. I've been watching updates closely this morning so when I updated Windows and SOSLIB, then saw ASHUPD on both updates, I thought I was playing dueling update centers and would have to rerun whatever I ran first. When I ran the various updates for Windows again, there were no additional updated of things that had already been updated.
|
|
|
|
Re: SOSUPD for UNIX
#28944
29 May 07 07:44 PM
|
Joined: Jun 2001
Posts: 11,645
Jack McGregor
OP
Member
|
|
OP
Member
Joined: Jun 2001
Posts: 11,645 |
OK, ASHUPD is now out of SOSLIB. When you run SOSUPD, if it detects any copies of ASHUPD in [901,2], it will ask you if you want them deleted. (ASHUPD is now part of the standard A-Shell release.)
I also added the developer help files to the SOSUPD update repository, on the theory that if you are using SOSLIB, you probably want the latest copies of the developer doc files as well.
|
|
|
|
Re: SOSUPD for UNIX
#28945
29 May 07 11:01 PM
|
|
Anonymous
Unregistered
|
|
Anonymous
Unregistered
|
Good stuff, Jack.
FYI there's a size zero SOSUPD.ZIP coming down in [907,10] that of course doesn't have the expected payload of fnhostexl.bsi.
Also if you run SOSUPD while in [901,2]start.cmd then the question to delete ASHUPD.* is answered with "RUN SOSDIR".
|
|
|
|
Re: SOSUPD for UNIX
#28946
30 May 07 12:03 AM
|
Joined: Jun 2001
Posts: 11,645
Jack McGregor
OP
Member
|
|
OP
Member
Joined: Jun 2001
Posts: 11,645 |
Thanks for the feedback. I think both issues are resolved in SOSUPD.RUN 2.1(108)
|
|
|
|
|
