Mainframegeek
Lets Geekout with Mainframe
Friday, December 14, 2012
Wednesday, December 12, 2012
Convert Gregorian Date (YYYYMMDD) to Julian date(YYYDDD) and vice versa
The easiest ways to convert Julian date (YYYYDDD) to Gregorian equivalent is using COBOL Intrinsic functions.
Here is the function and its descriptions.
Function | Description |
DATE-OF-INTEGER | Gregorian date equivalent (YYYYMMDD) of integer date |
DAY-OF-INTEGER | Julian date equivalent (YYYYDDD) of integer date |
INTEGER-OF-DATE | Integer date equivalent of Gregorian date (YYYYMMDD) |
INTEGER-OF-DAY | Integer date equivalent of Julian date(YYYYDDD) |
*** The integer date is a seven-digit integer with a range from 1 to 3,067,671. (dates ranging from January 1, 1601 thru December 31, 9999).
The Gregorian date is obtained from the calculation (YYYY * 10,000) + (MM * 100) + DD.
o YYYY represents the year. It must be an integer greater than 1600, but not greater than 9999.
o MM represents a month and must be a positive integer less than 13.
o DD represents a day and must be a positive integer less than 32, provided that it is valid for the specified month and year combination.
The returned value of INTEGER-OF-DATE/DAY functions is an integer that is the number of days the date represented by given input, succeeds December 31, 1600 in the Gregorian calendar.
Sample Program
IDENTIFICATION DIVISION. WORKING-STORAGE SECTION. A0100-MAIN-PARA. ACCEPT WS-JULN-DATE. |
Output
Hey Guys. if my tutorial helped you please support me by liking my facebook page, sharing this webpage with your friends and commenting below. If you want me to update or add me some specific tutorial please cooment to this page or email me at shibuthannikkunnath@gmail.com
-Cheers – Shbibu Thannikkunnath
Tuesday, December 4, 2012
IBM Mainframe Payroll Project
Are you looking for mainframe projects?, then this is the right place for you. Right now I have 2 Projects ( Mainframe projects with Source code ) coded with COBOL, have utilized LE xml service and GDGs. you might be able to tune these projects, so please post your valuable comments and snippets.
This is just a starting a series of mainframe projects, I’ll be uploading more projects in coming days. Also if you need a project or you have some suggestions please write to me at shibuthannikkunnath@gmail.com.
You might face few issues while uploading and running the applications and may think that the provided documentation is not enough. In those situations please drop me a mail at shibuthannikkunnath@gmail.com and I can help you to clear all the doubts regarding the projects.
1. MAINFRAME PAYROLL PROJECT.
This project is for generating calculating employee's salary and generate pay slip. This application will also generate xml log for the pay slips generated and can be used to monitor in future by feeding to xml log monitoring application or you can even send it to a web service!.
I have coded these applications in my machine and xmitted and downloaded them.
Step 1. Download the binary format source and and dependent files.
download link
http://www.mediafire.com/?6th6w35ns4lk182
The above zipped file contains a couple of binary files, download zip file and unzip it and keep the binary files in your local drive.
Step 2. Upload files to mainframe.
At this point of time I’m assuming that you have IBM personal communications installed in your machine, I mean any emulator is fine. Since I’m using PCOMM the I’m gonna explain from the PCOMM point of view ;).
Login to mainframe TSO session
Chose option 6 (command).
Now choose Actions from the Menu bar and select send file to host.
Click on browse and chose the first file from the zipped folder. and chose Binary as the transfer type for all files and click on update in list or add to list then click on send. Do not forget to put quotes before and after the server file name, this to avoid the automatic padding of your RACFID by zOS.
use the bellow server file name for all the respective files.
PAYROLL.CLAIMFLE
PAYROLL.EMPFILE
PAYROLL.JCLS
PAYROLL.PAYFILE
PAYROLL.SOURCE
PAYROLL.FLECPYBK
Step 3. Inflate the binary files.
Here we are expanding all the binary files to their original format, go to ISPF main option 6 (Command) and type
receive indsn(‘<binary filenames>’) , don’t forget the quotes
eg: receive indsn('PAYROLL.CLAIMFLE')
you will get a message like below one, just press Enter key
INMR901I Dataset TSHRCI.PAYROLL.CLAIMFLE from R0318B on N1
INMR906A Enter restore parameters or 'DELETE' or 'END' +
You will get a successful message like below. if not try again “ watch for the quotes”
INMR001I Restore successful to dataset 'TSHRCI.PAYROLL.CLAIMFLE'
repeat the step 3 for all the 6 files there in the downloaded zip file.
Step 4. we are almost there, verify the files
go to ISPF option 3.4, and type “TSHRCI.PAYROLL” in dsname level and press enter you will get a screen almost like below. except TSHRCI.PAYROLL.PAYSLIP.GROUP and TSHRCI.PAYROLL.XMLLOG.GROUP.
Step 5. Build the supporting GDGs
Go to TSHRCI.PAYROLL.JCLS and put an “e” in front of GDG and hit enter key.
right now this is the pay slip GDG JCL, so submit it to create pay slip GDGs
Now modify the JCL to below JCL (Changes are marked in red color) and submit it.
//R0318BJ JOB 'SHIBU THANIKKUNNATTH',NOTIFY=&SYSUID //SYSUT2 DD DSN=TSHRCI.PAYROLL.XMLLOG.GROUP(+1), |
Line marked in PINK color is the DASD volume, if your site is not SMS managed you have to provide the volume serial number, if you don’t know the vol ser, you can contact z box system admin.
Now if you go back to ISPF main option 3.4 and TSHRCI.PAYROLL.* you can see your screen as below.
Step 6. Time to review contents of all the datasets.
go to First file (TSHRCI.PAYROLL.CLAIMFLE) and you can see the below screen
This is the file which employees will claim their billed hours for a whole month. The structure is as given below
FD-CF-MONTH PIC X(03).
FD-CF-WEEK PIC X(01).
FD-CF-EMPID PIC X(10).
FD-CF-BILL-CDE PIC X(02).
FD-CF-SUN PIC X(03).
FD-CF-MON PIC X(03).
FD-CF-TUE PIC X(03).
FD-CF-WED PIC X(03).
FD-CF-THU PIC X(03).
FD-CF-FRI PIC X(03).
FD-CF-SAT PIC X(03).
First 3 chars for the month, Next 1 char for the week(1,2,3,4), next 10chars for employee id, entered ID should have an entry in TSHRCI.PAYROLL.EMPFILE, next 02 chars are for bill codes we can use bill code for claiming over time valid values( 01 for basic claiming, 02 for leave hours, 03 for week day overtime, and 04 for weekend over time) these bill codes should have matching entry in TSHRCI.PAYROLL.PAYFILE with band code of the employee. Next 7 fields of 3 characters are for daily hour claiming.
e.g. JAN1100000000101000008008008008008000
says: its for Jan First week, for employee ID 1000000001, basic hrs, and 0hrs for Sunday, 8 hrs each for Monday, Tuesday, Wednesday, Thursday, Friday and 0hr for Saturday.
Now go to TSHRCI.PAYROLL.EMPFILE, File structure is given below.
05 FD-EF-EMPID PIC X(10).
05 FD-EF-FNAME PIC X(10).
05 FD-EF-LNAME PIC X(10).
05 FD-EF-ADD1 PIC X(10).
05 FD-EF-ADD2 PIC X(10).
05 FD-EF-PH PIC X(13).
05 FD-EF-DOJ PIC X(10).
05 FD-EF-DOB PIC X(10).
05 FD-EF-LASTPAYED PIC X(10).
05 FD-EF-EMPMODE PIC X(03).
05 FD-EF-STATUS PIC X(03).
05 FD-EF-PAYMODE PIC X(01).
05 FD-EF-BAND PIC X(02).
First 10 bytes for employee id, next 10 for first name and next 10 for last name, next 10 for address line1 and next 10 for address line2, next 13 bytes for phone number, next 10 bytes for date of birth,, next 10 bytes for last paid month its for future enhancement. next 3 bytes for employment mode valid values are per for permanent and con for contract. next 3 bytes for status 001 is active and 002 is resigned, next 2 bytes for band can have any value but the band value should have a matching entry in TSHRCI.PAYROLL.PAYFILE.
Now go to TSHRCI.PAYROLL.FLECPYBK
This data set contains the file structures of all data sets, It has been created to refer the files at any point of time if you do not access to our web sites, and to avoid to messing up our code B)
Now go to TSHRCI.PAYROLL.JCLS
This PDS contains the JCL’s for compiling our code, running our application, creating GDG’s and deleting GDG’s. GDG operations has been explained in Step 5.
BATCHBOB.
This JCL can used to compile the cobol application, if the IGYWCL proc is in the 'SYS1.ADMIN.PROCLIB' and IGYWCL has been undergone some tweaks to accept member name, srce lib and load lib parms. right now this is the only cause in IBM internal training machines.
COBCPL.
I believe this JCL must work in almost all the mainframes that has IBM Cobol version 4.1. this job directly call the IGYWCl which is the part of COBOL ver 4.1 so it should work without making any noises.
“If you have any issues with writing compile JCL for our project please write back to me at shibu@hotmail.co.in I can always help you to get a fully functional compile JCL"
Execpgm
This JCL is for executing our application. If you go to this JCL you can see that I have commented out a couple of lines (//* VOL=SER=EUTDSD,) these are the volume serial numbers, since my machine is SMS managed I do not have to worry about the vol ser numbers, SMS will take care of it.
If your site is not SMS managed you have to un comment these line and change the volume serial number to the volume where GDGs resides. If you go to ISPF 3.4 option you can see volume at the right side of your dsn, see the below screen shot, for TSHRCI.PAYROLL.JCLS the vol ser is ETRU03.
GDG and GDGDEL
These are the JCLS for creating and deleting GDGs. PLease refer to Step 5 for more information.
Now go to TSHRCI.PAYROLL.PAYFILE
“Soon you opened the dataset please enter num off command in order to avoid any data lose"
This file is all about the MONEY, we have to declare the hourly charge for different bands.
File structure is
05 FD-PF-BAND PIC X(02).
05 FD-PF-HOURLY PIC X(04).
05 FD-PF-DAILY PIC X(04).
05 FD-PF-MONTHLY PIC X(06).
05 FD-PF-OVERTIME PIC X(03).
05 FD-PF-LEAVE PIC X(04).
05 FD-PF-WEEKENDOT PIC X(03).
First 2 bytes are for Ban number, next 04 bytes are for per hour charge for normal (8hrs per day) work hours if the guy is working as per hour plan, next 4 bytes are for per hour charge normal (8hrs per day) work hours if the employee is working in daily wage plan, and next 4 bytes are for per hour charge for normal work hours(8hrs per day) if the employee is working in monthly wage plan. next 3 bytes are the amount needs to bill if the employee worked week day over time. Next 4 bytes are the amount needs to charge if the employee went on vacation ( normally no company will reduce any amount from salary, so we) . next 3 bytes are for the amount needs to charge if the employee worked on weekend over time.
e.g. 05020010000300003000200100
The above line says band is 05, 200 for hourly wage, 1000 for daily wage, 3000 for monthly wage, 300 if employee was on week day over time, 200 if employee was on leave/vacation, and 100 if employee worked on weekend over time.
Now go to TSHRCI.PAYROLL.SOURCE
PDS contains the source code, you have all the freedom to work on the source code.
Please do not change the Author name!
Step 7 Most important: create load lib
Load lib is the pds where our compile and exec pgm JCL are pointing to. So let create it. This PDS will be same for all our projects so don’t be a miser, allocate few cylinders.
Go to ISPF 3.2 screen fill the screen as below
press enter
Ignore the management class, storage class, volume serial, device type, data class and fill out the remaining fields as in below screenshots
Press enter to finish it up.
We are done with the setups. now lets go and run the code!.
Step 8. Run the code
If you want you can edit claim file, if you want to claim your own billed hrs. but don't forget to add your own employees and band details also. Other wise app will abend!. :D. PLease be aware the code will work fine with the provided data.
Now go to TSHRCI.PAYROLL.JCLS and submit compile JCL
compile JCL should return MAXCC 0
after that submit EXECPGM jcl.
our program will return maxx cc 0, almost in all the cases, please review the data sets again if you have made any changes (Refer 5 and 6 to know the file structures and GDGs)
Go to spool and verify the claims processed flow and the data (if needed)
Now, its the time review the GDGs
Pay slip
Go to ISPF 3.4, DSNAME level TSHRCI.PAY* and open the latest TSHRCI.PAYROLL.PAYSLIP.GROUP.* gdg.
and you can see the pay slips generated for our employees, of the inputted month.
XMLLOG
go to ISPF 3.4, DSname level TSHRCI.PAY* and open the latest version of TSHRCI.PAYROLL.XMLLOG.GROUP
That' is it. keep exploring the project, do tweaking, but do not forget to write to me your experiences and your doubts or what ever related to mainframes at shibuthannikkunnath@gmail.com
Friday, November 30, 2012
Submit or Retrieve Jobs with FTP / Alternative For Remote Job entry (RJE)
This post is about an alternative for remote job entry, you can use the TCP/IP FTP service in zOS and a Shell/command prompt to retrieve, List, and submit Jobs to Mainframe.
Basic Commands used in this article
FTP - To start FTP
Open remore_system_ip - To connect to host via FTP
QUOTE site filetype=JES - Connect to JESPLEX, (conect to JES in layman terms)
DIR - List Jobs
Get filename - Get Job dataset from remote system
PUT filename - Submit Job
Make Sure that the FTP is up and running in your mainframe system.
You can do this by find the “TCPIP” job in your spool.
Connect to Mainframe via FTP
Open the command prompt/Shell and Enter FTP.
Enter Open your mainframe_host_ip
Enter your user ID followed by password
C:\>ftp Connected to demomvs.demopkg.ibm.com. |
At this point you are connected to MVS subsystem, if you issue a DIR you can see your MVS datasets, issue SITE FILETYPE=JES to get connected to JESPLEX
ftp> quote site filetype=jes |
Issue a DIR command to see the jobs.
Unlike SDSF, the dir command display the last ran job, first in the list
ftp> dir |
Issue DIR JOBID to see the files associated with the JOB
ftp> dir JOB01982 |
Issue GET JOBID.n “destination_file” to ftp the job files from Mainframe to your machine. If you issue GET JOBID.n (n is a number) you will get the nth file from JOB, if it is GET JOBID.X you will get all the files belongs to that JOB
ftp> get JOB01982.x "C:\temp1\JOB01982.x.txt" |
Issue PUT “JCLL_location” (JCLL_location is the JCL file path in your local machine). Eg. in my Machine the JCL is located at “C:\temp1\sort_jcl.txt”
ftp> put "C:\temp1\sort_jcl.txt" |
Issue DIR to see the latest JOB
250 Transfer completed successfully. |
Guys try this yourself, if this post helped you, don’t forget to Comment/like/share the page and of course visit the below advertisement.
Cheers- Shibu Thannikkunnath
Installing and configuring 3270 Terminal emulator in Mac
Step 1. Download 3270 client for MAC OSX
Download tn3270 from here - http://www.brown.edu/cis/tn3270/index.html#latest . When I’m writing this article the latest version of tn3270 is 3.3b6 (beta). It worked perfectly in my 2012(mid) Macbook pro Retina display.
Step 2. Mount the dmg and open the disk in finder.
Step 3. Copy tn3270x Application file to your applications folder
Step 4. Invoke tn3270x by double clicking on the application
Fill your hostname on “Host Name” field. By default the port will be 23, but if you want you can change the port number by clicking on “Special” Button
Once you are done with your settings, click on “open connection” Button.
I have used Fandezhi/efglobe mainframe, it is a free mainframe and can be used for your skills development. If you want to know more about creating an id, visit my post about getting a free mainframe id (http://mainframegeek.me/2012/11/23/free-mainframe-id-to-practice/)
That’s it; you know how to go from here J Hey guys, if this post helped you, subscribe for my posts, share it or like my Facebook page.
Cheers –Shibu-
Installing and configuring 3270 Terminal emulator in Mac
Tn3270 is absolutely free, you can download tn3270 from here - http://www.brown.edu/cis/tn3270/index.html#latest . When I’m writing this article the latest version of tn3270 is 3.3b6 (beta). It worked perfectly in my 2012(mid) Macbook pro Retina display.
Step 2. Mount the dmg and open the disk in finder.
Step 3. Copy tn3270x Application file to your applications folder
Step 4. Invoke tn3270 by double clicking on the application.
Fill your hostname on “Host Name” field. By default the port will be 23, but if you want you can change the port number by clicking on “Special” Button.
Once you are done with your settings, click on “open connection” Button.
I have used Fandezhi/efglobe mainframe, it is a free mainframe and can be used for your skills development. If you want to know more about creating an id, visit my post about getting a free mainframe id (http://mainframegeek.me/2012/11/23/free-mainframe-id-to-practice/)
That’s it; you know how to go from here
Hey guys, if this post helped you, subscribe for my posts, share it or like my Facebook page.
Cheers –Shibu-
Wednesday, November 28, 2012
Declare numeric field with More than 18 Digits in Cobol
Well you can override it in Enterprise Cool, or in other words if Language environment (a.k.a LE) is available at your shop. The Language environment is introduced back in 2000 by IBM, which is a common application layer for many Programming languages. The LE has a lot of cool features which I’ll be covering future posts. So keep coming back.
Here is a sample program for Numeric field declaration with more than 18 digits. The Compiler directive (CBL) is that really turning the ship around.
This compiler-directing statement selectively suppresses output or causes output to be produced. The keywords *CONTROL and *CBL are synonymous.
The Program logic is simple its just move a 31 digit number to the number 1 variable, then add it with itself and display it.
If you Don’t have mainframe access to try it out, visit my post on getting a free mainframe id, it really helps. http://mainframegeek.me/2012/11/23/free-mainframe-id-to-practice/ . It’s a raw mainframe so you won’t be getting handy compile JCL on this mainframe, let me know if you need one, I can help you.
CBL ARITH(EXTEND) IDENTIFICATION DIVISION. PROGRAM-ID. COB18DIG. AUTHOR. SHIBU.T. * DATA DIVISION. WORKING-STORAGE SECTION. 77 WS-NUM1 PIC 9(31). * PROCEDURE DIVISION. A0000100-MAIN-PARA. MOVE 1234567890123456789012345678901 TO WS-NUM1. DISPLAY 'WS-NUM1 BEFORE ADDITION: ' WS-NUM1. ADD WS-NUM1 TO WS-NUM1. DISPLAY 'WS-NUM1 AFTER ADDITION: ' WS-NUM1. STOP RUN. |
The compile and run JCL will complete with return-code 000, here is the output I got in my machine.
Does my Program, post helped you? Comment, rate or like my facebook page (top right corner of this page) and click on the adds listed below. It really help me to make this website alive.
-Cheers, Shibu