home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 8 Other
/
08-Other.zip
/
ALMCPY.ZIP
/
ALMCPY.TXT
Wrap
Text File
|
1992-03-06
|
5KB
|
84 lines
Since little documentation seems to be publicly available for
ALMCOPY as released in the ES 402 EEP, I have included some information
available from an earlier release of ALM to facilitate its installation
and use. This information is based upon installation instructions I
received when we licensed ALMCOPY 5.4B from IBM almost two years ago.
I have used this method to upload the MODULEs and EXEC's for the ES
applet, and it DID work.
For starters, please recognize that the ALMCOPY.ZIP file found on
diskette 1 of the ES package includes both workstation AND VM-host files.
The file types can be determined by the extensions. An explanation is
included below:
PC-extension = .MOD Host MODULE file
PC-extension = .EXC Host EXEC file
PC-extension = .REX Host REXXEXEC file
PC-extension = .NAM Host NAMES file
PC-extension = .EXE PC executable file
PC-extension = .DLL PC DLL file
PC-extension = .C Source code for ALMCOPY front-end
PC-entension = .H Header files for ALMCOPY front-end
PC-extension = .MSC Make file for ALMCOPY front-end
Now that you know where the files belong and what they are, there are
are some special considerations you MUST observe to get everything up
to the VM host properly. First, be aware that the modules included in the
ALMCOPY.ZIP file are in a TERSED format. This means that they were "packed"
on the VM host before being downloaded for inclusion in the ALMCOPY.ZIP
file. This was done to preserve the MODULE characteristics defined for the
file on VM when it was compiled and linked. Also, please note that the
.EXC, .REX and .NAM files are also in a TERSED format. Now for the good
part! To upload these guys and make them usable, do the following:
1. Upload these modules with SEND to your favorite VM host.
When you upload them, do NOT specifiy ASCII-EBCDIC translation as
these files are BINARY!!!! Also, you MUST specify an LRECL size of
1024. Your PC command should look like this:
SEND ACXFR56B.MOD A:ACXFR56B MODPACK A ( LRECL 1024 <enter> etc..
2. When you upload these files, use the following conventions for the
VM filetype specification...... concatenate PACK to the PC file
extension. IOW - ACXFR56B.MOD becomes ACXFR56B MODPACK,
ALMCOPY5.REX becomes ALMCOPY5 REXPACK, etc.......
3. Once you have the files uploaded, do a FILELIST on your A-Disk
(or wherever you uploaded your files to) as follows:
FILELIST * *PACK <enter>
This should give you a list of the files you just uploaded from
your PC. Now, you need to unpack them.
4. With your cursor next to the first file, type the following VM
command to "UNPACK" the files.
COPYFILE / = filetype = ( UNPACK <enter>
You should use the following conventions for specifying the
appropriate filetype:
MODPACK = MODULE REXPACK=REXXEXEC EXCPACK=EXEC
NAMPACK=NAMES
5. PF3 your way back to a RUNNING state after successfully unpacking
all of your ALMCOPY files.
6. Voila! You're done... Now, drop back to the PC, make sure that
ALMCOPY.DLL is in your LIBPATH, and do the following:
ALMCOPY ALMCOPY.* Hx:= = = <enter>
(where x: is your Host session identifier).
Watch the fun! ALMCOPY is smart enough to recognize that different
files should be handled in different fashions. It is smart enough
to know that .EXE and .DLL files should be uploaded as binary files
and does it automatically! The secret is the ALMCOPYX NAMES file
on the host. ALMCOPY uses this file to figure out file name
extension conversions on VM, binary vs. ASCII uploads, etc....
ALMCOPY has a number of processing options which I assume will be
documented in the GA release. Hopefully, IBM will take the ALMCOPY
documentation and turn it into an .INF file for VIEWing purposes.
***** Dave Whittle, are you reading this????? *****
Please don't interpret this entry in the forum as comprehensive. I
assure you it is NOT! However, this will at least get it installed for you,
and allow you to begin trying it out. Hopefully, as usage questions
arise, various existant (sp?) users will chime in with answers. I'll
chime in as well, and hopefully contribute my experiences with the tool.
Try ALM out, I think you'll find it an extremely versatile tool. If
you have access to an IBM SE, ask him/her about it. Chances are, they
probably use it everyday!
Good luck!
Toby Pennycuff
American Airlines