Mainframe Data Transfer Expert Needed
Budget: €30 – €250 EUR
I'm seeking a skilled professional with extensive experience in mainframe data management.
This assignment includes: create files or scripts that interact directly with the mainframe, meaning:
-
Create files: Use JCL to generate and manipulate datasets on the mainframe. For example, a JCL script that extracts data from one dataset and saves it into another.
-
Read files: Develop a program in COBOL or Python to analyze data in an existing dataset.
-
Transfer files: Use Zowe CLI or a similar tool to transfer files between your local system and the mainframe.
-
REXX: Create an automated script to monitor system logs in real time.
For this, you need to submit all source files, output files, job logs, and README files. Based on these files, someone with Advanced/Extended Level knowledge should be able to execute your project.
You must also submit a single-page flyer, as specified in the assignment:
You’re going to design a single-page flyer that tells us the
following information, in your own style:
1: What you call your creation
2: What it does
3: Why it’s AWESOME
Use screenshots, graphics, big fancy text, whatever you like to get us excited about your
fantastic creation. Being able to clearly illustrate your work is an *incredibly* important
skill in business. People need to be excited about something before they’ll want to try it
out, and they need to see it working before they know it’s worth telling others about.
Coming up with an idea and making it a reality is going to involve some serious effort.
Make sure it gets noticed and used the way you want it to by spending a portion of that
time writing it up.
Restrictions:
Title : 100 characters Notes: 500 characters
Directions: 1500 Characters
Flyer: 5MB in size, JPG, PNG, GIF file format
Here’s a demonstration of the level of detail you should consider when writing up your work.
Title: Snapshot and Restore-o-Matic
Notes: An Ansible playbook, with supporting Python code, which lets a user
make “snapshots” of their progress through a challenge, saving any indicated
changed data sets and members, then letting them restore to a known saved
state later on, if they want to re-try a challenge from scratch or go back to a
“known good state”.
Directions: Download the Ansible playbooks titled “checkpoint” and “restore”
from my USS home directory in /z/Z99999. When run, the checkpoint play
book will grab everything up in the INPUT, SOURCE, WORK, and JCL data
sets, as well as user-created content in the USS home directory and back
them up in a tarball with the current date and time. By default, the restore
playbook seeks the newest backup and moves all of the data sets, members,
files and folders back where they were at the time of backup.
You will create a screencast where you show the source files and explain how they work. Afterward, you will give a demo of your program. Important: All files must be readable in ASCII or UTF-8 (no EBCDIC). Only submit source and output files that you have generated on the system yourself. Ensure your submission is not generic. Use a unique layout, original search actions, and meaningful counts. Keep in mind that IBM may sometimes schedule maintenance on the mainframe for a day. Include a basic README with the necessary instructions to start your program.
This assignment includes: create files or scripts that interact directly with the mainframe, meaning:
-
Create files: Use JCL to generate and manipulate datasets on the mainframe. For example, a JCL script that extracts data from one dataset and saves it into another.
-
Read files: Develop a program in COBOL or Python to analyze data in an existing dataset.
-
Transfer files: Use Zowe CLI or a similar tool to transfer files between your local system and the mainframe.
-
REXX: Create an automated script to monitor system logs in real time.
For this, you need to submit all source files, output files, job logs, and README files. Based on these files, someone with Advanced/Extended Level knowledge should be able to execute your project.
You must also submit a single-page flyer, as specified in the assignment:
You’re going to design a single-page flyer that tells us the
following information, in your own style:
1: What you call your creation
2: What it does
3: Why it’s AWESOME
Use screenshots, graphics, big fancy text, whatever you like to get us excited about your
fantastic creation. Being able to clearly illustrate your work is an *incredibly* important
skill in business. People need to be excited about something before they’ll want to try it
out, and they need to see it working before they know it’s worth telling others about.
Coming up with an idea and making it a reality is going to involve some serious effort.
Make sure it gets noticed and used the way you want it to by spending a portion of that
time writing it up.
Restrictions:
Title : 100 characters Notes: 500 characters
Directions: 1500 Characters
Flyer: 5MB in size, JPG, PNG, GIF file format
Here’s a demonstration of the level of detail you should consider when writing up your work.
Title: Snapshot and Restore-o-Matic
Notes: An Ansible playbook, with supporting Python code, which lets a user
make “snapshots” of their progress through a challenge, saving any indicated
changed data sets and members, then letting them restore to a known saved
state later on, if they want to re-try a challenge from scratch or go back to a
“known good state”.
Directions: Download the Ansible playbooks titled “checkpoint” and “restore”
from my USS home directory in /z/Z99999. When run, the checkpoint play
book will grab everything up in the INPUT, SOURCE, WORK, and JCL data
sets, as well as user-created content in the USS home directory and back
them up in a tarball with the current date and time. By default, the restore
playbook seeks the newest backup and moves all of the data sets, members,
files and folders back where they were at the time of backup.
You will create a screencast where you show the source files and explain how they work. Afterward, you will give a demo of your program. Important: All files must be readable in ASCII or UTF-8 (no EBCDIC). Only submit source and output files that you have generated on the system yourself. Ensure your submission is not generic. Use a unique layout, original search actions, and meaningful counts. Keep in mind that IBM may sometimes schedule maintenance on the mainframe for a day. Include a basic README with the necessary instructions to start your program.