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 dependant 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.
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.
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.
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
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.
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!.
. 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
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 dependant 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 //GROUP EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSIN DD * DEFINE GDG(NAME(TSHRCI.PAYROLL.XMLLOG.GROUP)- LIMIT(3) - NOEMPTY - SCRATCH) /* //MODEL EXEC PGM=IEFBR14 //GDGMODEL DD DSN=TSHRCI.PAYROLL.XMLLOG.MODEL, // DISP=(NEW,CATLG,DELETE), // UNIT=SYSDA, // SPACE=(TRK,0), //* VOL=SER=EUTDSD, // DCB=(LRECL=80,RECFM=FB,BLKSIZE=800,DSORG=PS) //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //GDS EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //SYSUT1 DD * RECORD-100001 RECORD-100002 /* //SYSUT2 DD DSN=TSHRCI.PAYROLL.XMLLOG.GROUP(+1), // DISP=(NEW,CATLG,DELETE), // SPACE=(TRK,5), // DCB=TSHRCI.PAYROLL.XMLLOG.MODEL, //* VOL=SER=EUTDSD, // UNIT=SYSDA //SYSIN DD DUMMY // |
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!.
. 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 dukkasrinivasyadav@gmail.comAdvertisement
No comments:
Post a Comment