This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
// compile the source code | |
var compile_rules = require("bldz/std/exp/rules/compile").cobol().rules; | |
// bind the object files | |
var bind_rules = require("bldz/std/exp/rules/binder").bind({ | |
deps: compile_rules, | |
outs: ["hey-cobol"], | |
syslibs: ["//CEE.SCEELKED"] | |
}).rules; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Manditory division - Identify the program | |
IDENTIFICATION DIVISION. | |
PROGRAM-ID. HELLOCBL. | |
* Optional division - Define they source computer and the | |
* target/build computer | |
ENVIRONMENT DIVISION. | |
CONFIGURATION SECTION. | |
SOURCE-COMPUTER. ZOS. | |
OBJECT-COMPUTER. ZOS. | |
* Optional division - define working variables, etc. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
host: the URL or IP of the L-PAR that you will be using. For example: lpar001.mycompany.com | |
user: your account name to logon the L-PAR. | |
zospath: the full path to the bin folder that we created previously | |
sync: | |
- id: test | |
remote: the USS path where you have full access. For example: /usr/myname/test/hello-cobol | |
local: ./ | |
dos2unix: true |