README.TXT -- Audust 24, 2020 Notice: More changes August 24, 2020 Added DB2 11 and 12, updated Taxonomy for DB2, MQ and Websphere. August 20, 2020 Added MQ and Websphere May 4, 2020 Separated Japanese and English Provided PDFs in a directory and links to them from KC doc pages for z/OS 2.4 and 2.3 July 23, 2019 Added SSLTBW_2.4.0.jar z/OS 2.4 base and features June 4, 2019 Added SSGMCP_5.4.0.jar CICS Transaction Server 5.4 Notice: Changes to the process of obtaining KC4z content plug-ins: Obtaining and using product documentation in KC4z plug-ins from FTP/HTTP/HTTPS directory: July 2018 1) ftp://public.dhe.ibm.com/systems/z/zos/sftp/kc/zosv2r3/ changes to: ftp://public.dhe.ibm.com/systems/z/zos/sftp/kc/ 2) zosv2r3_current.jar changes to SSLTBW_2.3.0.jar 3) installation target content/zosv2r3 changes to content/SSLTBW_2.3.0 4) receive.sh changes to receive.sh $1 to accept jar file prefix parameter. The JAR files in this directory contain Knowledge Center formatted product documentation. The receive.sh shell script provides an example download and extract script appropriate when your server has an internet connnection. JAR File: Product: SSEPEK_11.0.0.jar DB2 for z/OS 11 SSEPEK_12.0.0.jar. DB2 for z/OS 12 SSFKSJ_9.2.0.jar IBM MQ for z/OS SS7K4U_9.0.0.jar IBM Websphere Application Server SS7K4U_liberty.jar IBM Websphere Liberty Profile SS3H8V_1.1.0.jar IBM Open Data Analytics for z/OS SSDTBM_3.2.0.jar GDDM SSENW6_1.6.0.jar HLASM SS4SVW_3.0.0.jar z/OS Connect Enterprise Edition V3.0 SSGMCP_5.3.0.jar CICS Transaction Server 5.3 SSGMCP_5.4.0.jar CICS Transaction Server 5.4 SSLTBW_2.4.0.jar z/OS English 2.4 base and features SSLTBW_2.4.0.pdf.jar z/OS English 2.4 PDF files SSLTBW_2.4.0.jpn.jar z/OS Japanese 2.4 base and features SSLTBW_2.4.0.jpn.pdf.jar z/OS Japanese 2.4 PDF files SSLTBW_2.3.0.jar z/OS 2.3 base and features SSLTBW_2.3.0.pdf.jar z/OS English 2.3 PDF files SSLTBW_2.3.0.jpn.jar z/OS Japanese 2.3 base and features SSLTBW_2.3.0.jpn.pdf.jar z/OS Japanese 2.3 PDF files SSLTBW_2.2.0.jar z/OS 2.2 base and features ( English and Japanese ) SSLTBW_2.1.0.jar z/OS 2.1 base and features ( English and Japanese ) Under the regime of continuous delivery, files in this directory are intended to be updated weekly, when appropriate. To refresh your KC4z with the most current documentation, repeat the download and extract of the updated .jar file After downloading and installing this product documentation, you can deploy it on one or more KC4z instances. The KC4z instance(s) will then serve it to browser clients. The following instructions describe how to download, install, and deploy the KC4z plug-ins. Make Space available first ------------------------------------------ The content for z/OS V2R3 Base and Features will require slightly more than a gigabyte. The SSLTBW_2.3.0.jar delivery file will require about 900 megabytes. A cylinder is roughly .75 megabyte. Therefore, the 2000 (rounded up) megabytes for the z/OS 2.3 content and the SSLTBW_2.3.0.jar required at the moment of delivery should fit within 2700 (rounded up) cylinders. This is well within the amount (3200) allocated by the HKCDATGZ sample job. However, this might be the case ONLY if the V2R3 content will be the ONLY content installed. For example, if you participated in the ESP program for z/OS 2.3, you should remove the ./content/ESPV2R3 subdirectory tree. If you downloaded and installed from this site before the July 13 2018 changes, you should remove the ./content/zosv2r3 subdirectory tree. If you had a filesytem mounted at ./content/zosv2r3 you should mount that file system at ./content/SSLTBW_2.3.0 instead. To add future additional content, we recommend creating and mounting a file system for each product's content at a carefully named mount point under the /global/kc4z/data/content/ directory. For example, if a product jar file to be installed contains a content/cics subdirectory, the mount point should be named /global/kc4z/data/content/cics If you wish, to manage the space for SSLTBW_2.3.0 ( z/OS V2R3 ) outside the zfs allocated by HKCDATGZ an 1400 cylinder zfs mounted at /global/kc4z/data/content/SSLTBW_2.3.0 should be sufficient. The skills to perform the zfs allocation and mount tasks can be acquired by studying, copying and modifying the HKCDATGZ sample job shipped with KC4z. A systems programmer needs to create an parmlib entry so the new filesystem will be mounted automatically during an IPL. Manually Download a content JAR file to your z/OS system: ------------------------------------------ Issue the following commands from within your /global/kc4z/data/ directory default (or other directory under which you'll install the KC4z plug-ins) on your z/OS system. This will download plug-in JAR file (SSLTBW_2.3.0.jar, for example ) from the public.dhe.ibm.com kc4z FTP site into that directory. Note that creating and updating files under /global/kc4z/data is most easily accomplished when using a "root-like" user ID. Note also: these manual steps (and more) are embodied in the receive.sh shell script in this directory. Skip ahead in this document to read instructions about using receive.sh. cd /global/kc4z/data/ ftp public.dhe.ibm.com anonymous (Enter your email as your password) dir cd systems/z/zos/sftp/kc/ binary get SSLTBW_2.3.0.jar quit Install the plug-ins into your KC4z repository: ----------------------------------------------- Run the appropriate command for the jar file that you obtained, keeping in mind the following items: - The user ID that you use to run the jar command will be the owner of the resulting files and directories. - The permissions of the files that are extracted from the jar file are set to 644 and directories 755. - KC4z does not write under the resulting directory tree. -- After you downloaded SSLTBW_2.3.0.jar, issue the following command from within the same directory as above (/global/kc4z/data/ by default): umask 022 jar -xf SSLTBW_2.3.0.jar This creates(or updates) an SSLTBW_2.3.0.properties file in your /global/kc4z/data/conf/ directory, creates(or updates) an SSLTBW_2.3.0/ subdirectory in your /global/kc4z/data/content/ directory, and populates content/SSLTBW_2.3.0/ with all of the V2R3 plug-ins and ditamaps as well as an empty pdf/ subdirectory. Note that this "jar -xf" command assumes that "/global/kc4z/data/SSLTBW_2.3.0.jar" is the fully qualified path name of the downloaded SSLTBW_2.3.0.jar file. Example shell script: receive.sh ----------------------------------------------- When the destination system for the KC Content has an open connection to the internet, receive.sh can be downloaded (ascii) and used to perform these commands. Within receive.sh, replace "yourID@your.host.com". Set permissions for receive.sh to allow execute and run. "receive.sh SSLTBW_2.3.0" gets and unjars SSLTBW_2.3.0.jar. Be sure to run "receive.sh SSLTBW_2.3.0" with /global/kc4z/data set as the current working directory. Deploy the plug-ins by connecting them to KC4z: ----------------------------------------------- If you have followed these instructions exactly and used the default /global/kc4z/data/ directory as the location for the KC4z data subdirectories, you are ready to run. Ensure that you start the hkcsvr1 (KC4z Server) started task if it is not already running. However, if you extracted SSLTBW_2.3.0.jar to a different directory, for example /u/your/directory/, you must first complete the following steps to deploy the plug-ins: 1) If the hkcsvr1 (KC4z Server) started task is running, stop it. 2) Update the /etc/kc4z/servers/kc4zServer/kc.properties file to append the extracted conf directory (/u/your/directory/conf) to the conf.path keyword value, for example: conf.path=/global/kc4z/data/conf,/usr/lpp/kc4z/kc4z.infocr/conf,/u/your/directory/conf Note that conf directories in the conf.path value are comma delimited. 3) Start the hkcsvr1 (KC4z Server) started task. View the product documentation in a browser client: --------------------------------------------------- Use the URL that is echoed in the KC4z Server console.log file, according to the KC4z product documentation, to view the product documentation in a browser client: -- Knowledge Center format: At the "Knowledge Center Product Documentation" link in the KC4z for V2R3 Table of Contents Optional instructions for connecting PDF links in KC4z to local PDFs: ------------------------------------------------------------------------- When using KC4z to view Knowledge Center formatted product documentation, each product has a landing page that lists links to one or more PDFs for that product's documentation. These links serve a local copy of the selected PDF if it resides in the /global/kc4z/data/content/SSLTBW_2.3.0/pdf/ directory. If the selected PDF is not found in that directory, it is instead served from an IBM owned and managed remote repository. So, to enable local access to the PDFs that are listed on the KC4z product landing pages, move or copy the PDFs that you downloaded from IBM Customer Connect into the /global/kc4z/data/content/SSLTBW_2.3.0/pdf/ directory. As previously described, this initially empty pdf/ subdirectory is created when SSLTBW_2.3.0.jar is extracted with jar -xf. Special Usage Notes: --------------------- Any manual change made to the content in /global/kc4z/data/content/SSLTBW_2.3.0 (outside these instructions) requires running a "touch /global/kc4z/data/conf/SSLTBW_2.3.0" to activate those changes on the KC4z server. In some cases the /var/kc4z/runtime/index and /var/kc4z/runtime/diskcache files may not be created correctly. Searches and automatic TOC synchronization may fail. In these cases, force KC4z to redo the index and diskcache creation with these three steps 1. Stop the HKCSVR1 started task, 2. Remove the files in the index and diskcache subdirectories. 3. Restart HKCSVR1.