pscobol

Table of Contents

1. Description
2. Setup - The basics of getting started with pscobol
   • Setup requirements
   • Beginning with pscobol
3. Usage - Configuration options and additional functionality
4. Limitations - OS compatibility, etc.
5. Development - Guide for contributing to the module
6. Changelog

Description

This module adds resources capable of administering Micro Focus Visual Cobol installation, including installation and removal of Micro Focus Visual Cobol, installation of patches and registration of licenses. It also provides capability to compile PeopleSoft Cobol.

Setup

Setup Requirements

To use pscobol module on windows, powershell provider is required, as much of the code is written in powershell. Depending on the version of your Windows operating system, you may be required to download and install, the following modules from the forge:

• "puppetlabs/powershell"
• "puppetlabs/pwshlib"

Beginning with pscobol

To start using the module, simply install the to your modulepath, e.g.

puppet module install puppetlabs-powershell --modulepath <your module path>
puppet module install puppetlabs-pwshlib    --modulepath <your module path>
puppet module install umaritimus-pscobol    --modulepath <your module path>

Usage

Here's a complete example of installing Micro Focus Visual Cobol Built Tools, updating it with the patch and registering the license.

We have the installer, patch and license file download to a \\share directory on windows. We would like to install Micro Focus Visual Cobol Built Tools into d:\cobol location.

We can register all these parameters in our hiera by adding these values into a yaml file within the data hierarchy:

---
pscobol::ensure:        'present'
pscobol::installdir:    'd:/cobol'
pscobol::package:       '//share/vcbt_40.exe'
pscobol::patches:       ['//share/vcbt_40_pu04_196223.exe']
pscobol::license:       '//share/PS-VC-WIN-VSTUDIO.mflic'

The module could also be called from a command line. Here's the example of compiling cobol in PS_HOME and PS_APP_HOME. The PS_APP_HOME is already defined in the environment, but we would like to use a compiled routine from a newly upgraded PS_HOME. The Visual Cobol compiler is installed in d:\cobol in this example:

puppet apply --modulepath <your module path> -e "class { 'pscobol' : ensure => 'present', targets => ['PS_HOME','PS_APP_HOME'] , installdir => 'd:/cobol', ps_home => 'd:/oracle/product/psft/pt/8.57.12' , }"

Note:

• The paths are strings, written in the Unix path format.
• Parameters ensure and package are required.
• Parameters ps_home, ps_app_home and ps_cust_home are only required when overwriting predefined environment variables.
• If patches is not specified, no patches will be applied. It's an array, so multiple patches could be specified.
• If license is not specified, no licenses will be registered in the license manager.
• If installdir is not specified, the installation target will default to the Program Files location,e.g. 'C:\Program Files (x86)\Micro Focus\Visual COBOL'

To uninstall Micro Focus Visual Cobol, simply replace the ensure value of 'present' by 'absent'

For additional usage, please see /examples/ in the source repository

Limitations

• Module pscobol was only tested for deployment of Micro Focus Visual Cobol Built Tools, but should work for others...
• It is known to work on Microsoft Windows Server platform, but should work on Mirosoft Windows 10 and Mirosoft Windows 11
• This module was tested on Puppet 8.6.*

Development

• Module pscobol was developed using PDK 3.0 on Windows OS.
• It's released under an open MIT license. So, please feel free ot use it freely.
• Please do send the Pull Requests to add functionality for other platforms.

Changelog

For updates please see the changelog