 The MVS Wrokbench and Files Organizer tool package (Version 7.6):
 -----------------------------------------------------------------

 README File: How to install and how to start using this tool. 


 (1) Restore six PDS tool library files on MVS host: 
 
 After you use the WinZip program to unzip the ZIP file, including
 this file totally ten PC files will be shown. Among them nine are the 
 PDS tool library files in the binary code format, which are:
 
 PRJCEXE1.XMT   ->	USERID.@PROJWRK.CEXEC.TOP
 PRJCEXE1.XMT   ->	USERID.@PROJWRK.CEXEC.BOT
 PROJEXE1.XMT   ->	USERID.@PROJWRK.EXEC.PART1
 PROJEXE1.XMT   ->	USERID.@PROJWRK.EXEC.PART2
 PROJDOCU.XMT   ->      USERID.@PROJWRK.DOCUMENT
 PROJLOAD.XMT   ->      USERID.@PROJWRK.LOAD
 PROJPANL.XMT   ->      USERID.@PROJWRK.PANELS
 PROJSKEL.XMT   ->      USERID.@PROJWRK.SKELS
 PROJTABL.XMT   ->      USERID.@PROJWRK.TABLE
 
 These nine files should be uploaded to your MVS/TSO host and XMIT in 
 the ASCII Binary FB-80 format, and the result upload.dsn files on the 
 MVS/TSO host should be the sequential files in FB-80 format. On MVS,
 you need  to issue the following command to restore each sequential file
 back to the PDS format:
 
 TSO RECEIVE INDA(upload.dsn)  or  RECEIVE INDA(/) on ISPF 3.4 option
 
 where upload.dsn are: USERID.PROJCREX.XMTBIN, USERID.PROJDOCU.XMTBIN,
 USERID.PROJLOAD.XMTBIN, USERID.PROJPANL.XMTBIN, USERID.PROJSKEL.XMTBIN,
 and USERID.PROJTABL.XMTBIN, etc. 

 Please refer to the attached XMT.Method MS Words document file for more 
 detail information of how to upload these files.

 After executing the 'TSO RECEIVE' command on MVS, the result PDS library 
 file names of each PC tool file on MVS should be named as the file names
 described on the right-hand side of the above '->' notations, where USERID 
 is your TSO Logon Userid.
 
 =========================================================================
 NOTE:
 Since the size of the @PROJWRK.CEXEC and @PROJWRK.EXEC files are too
 large, they have been split into two parts, and the total size of these 
 nine files and few document files are also too large and they have been 
 split into few Zip files.

 After you have successfully upload the @PROJWRK.EXEC part 1 and part 2
 files and the @PROJWRK.CEXEC top and bot files, you need to merge these
 four files into two PDS files named USERID.@PROJWRK.CEXEC and 
 USERID.@PROJWRK.EXEC, where the CEXEC is the compiled version of the REXX 
 source code EXEC file. 
 ==========================================================================   
         
 
 (2) Make a copy of three Text files on MVS host:
 
 The file names of the other three PC files of this tool package are:
 
 @PROJWRK.ANN   ->      USERID.@PROJWRK.ANNOUNCE
 @PROJWRK.PAC   ->      USERID.@PROJWRK.PACKAGE
 PROJ.EXC	->  	USERID.PROJ.EXEC

 These are the text files which should be uploaded in Text FB-80 dataset
 format to your MVS host, and the result files should all be in sequential 
 file format. The file names of each of these PC files on MVS should be
 renamed to the file names as described on the right-hand side of the 
 above '->' notations, where USERID is your TSO Logon Userid. For example, 
 you should rename the USERID.@PROJWRK.ANN file to USERID.@PROJWRK.ANNOUNCE
 and USERID.@PROJWRK.PAC file to USERID.@PROJWRK.PACKAGE. Notice that these 
 three files must be uploaded to MVS using the Text Mode (or ASCII Mode) 
 but not the Binary Mode.
 
 
 (3) Create an executable 'PROJ' command on TSO:  
 
 On MVS, you need to copy the USERID.PROJ.EXEC file to a member named
 'PROJ' in your Logon CLIST library so that it can be accessed in your TSO 
 session as a TSO command. For example, the name of this new member file
 can be: USERID.LOGON.CLIST(PROJ), where USERID.LOGON.CLIST is your TSO
 Logon CLIST library. If you don't have such a library file, it is highly
 recommended that you should create one.
 
 
 (4) In ISPF session, issue a 'TSO PROJ' command to start using this tool: 
 
 More detail information about the usages of this tool can be found in the 
 USERID.@PROJWRK.DOCUMENT library when you display that file on a PANEL4
 panel. There are two versions of the document, i.e. the SCRIPT version 
 and the HTML versions, available in this library. If your MVS site does 
 not provide the BookMaster for you to read the SCRIPT document, then you
 may download the HTML files from this library to your PC and read them. 
 The three PDF files for the Acrobat provided in the 'Document Download'
 page of this website are the copies of the HTML files, which can also be 
 used for you to obtain the detail information of this tool. 
 
 It is assumed that you have already reviewed the Highlight PDF file at
 this time and know what are the PANEL1, PANEL2, PANEL3, PANEL4, and 
 PANLE5 panels of this tool pacakge. On any of these panels, you may enter 
 a 'PH' command to display the online tutorial guide of this tool package. 
 
 You may select the 'PROJECT' sample project from the PANEL2 panel to 
 display a PANEL3 panel, and then display the PANEL4 panel of the 
 USERID.@PROJWRK.CEXEC library from the PANEL3 panel. Then next to each 
 member of this library you may type a '?' command to see the online 
 tutorial of each command provided by this tool package. Note that on the
 top of this CEXEC library on the PANEL4 panel it contains several sample
 REXX programs which are not in the compiled code format. These sample
 programs are used for invoking the HELPBOX, ITEMBOX, MEMUBOX, and MSGBOX
 facilities. Instead of using the '?' command, you may type a 'B' command 
 to browse these program files for reference.
 
 You may also enter a 'WHAT' command on any of these panels to display a 
 Command Sheet panel, on which it contains a list of the most frequently 
 used TSO/ISPF commands and Edit Macros that are provided by this tool 
 package.
 
 
 (5) Please make suggestions and/or contributions: 
 
 This tool package is not only very suitable for your personal use, but
 also can be used by your entire Software Development organization. After 
 you install this tool package on your own TSO account and become very 
 familiar with it, then you may consider install this tool package on a 
 TOOLS account for your Department or Division and teach all of your team 
 members to learn how to use this tool. If you find any problems with this
 tool package, please inform me to fix it. 
 
 Thank you for using this tool package. Good luck to you! If you find this
 tool package is useful, and wish to develop a set of Tutorial Slides or
 Foils to teach others how to use it, or wish to contribute some User-Exit
 programs, which you feel that it can be included in this tool package to 
 benefit other users in the world, then please don't hasitate to contact 
 with me. If that is the case, you need to release your program source code 
 to me in an email and grant me the right to redistribute it in writing,
 and also give me the permission to present your name in the "Contributors"
 page of this website. 
 
 

 Author:
 -------

 Nicholas L. Sun
 32 Carriage Hill Lane, Poughkeepsie. NY. U.S.A.
 (845) 473-5257
 email address: nsun12603@yahoo.com

 ---------------------------------------------------------------------
 The material of this tool package is a proprietary software product
 of the author, who is solely responsible for maintaining this tool
 and fix all reported problems.
 ---------------------------------------------------------------------
