My development team was involved in a project years ago that required migrating 200 Configuration Items (CI's) such as JCL, PROC, SYSIN Cards, Source code, DBRMLIB members, Loadlib members, not to mention running BIND Packages on DB2 programs. The scarier part is that the migration needs to be done in a day. Our installation does not have a tool to help us migrate CI's so everything had to be done manually.
Syncsort Windows Manual Download
- Click to browse our industry-leading research on Big Data, Hadoop, ETL, data integration, and much more.
- Read Online Ibm Syncsort Unix Manual Ibm Syncsort Unix Manual As recognized, adventure as without difficulty as experience just about lesson, amusement, as without difficulty as concurrence can be gotten by just checking out a books ibm syncsort unix manual then it is not directly done, you could put up with even more re this life, in the region of the world.
Plurareyes 4 fshare. Syncsort Manual From Long This is an application for Windows, providing automatic and manual IP-address update on Your XName account Syncsort Backup Express Syncsort Windows Manual.
The way we did this before this project was to keep a list of CI's to be migrated and days before migration, we would prepare the JCL, two people will go through the list, making sure that all the CI's are listed.With the risks involved, I needed to come up with a way to make sure all the CI's are migrated correctly and accurately. I figured that if I can keep a list of the items to be migrated, from what PDS's, and the dependent components to be migrated, and then use that list to generate a JCL to migrate the components, I can use that list through the SDLC process.
Enter SYNCSORT (or DFSORT)
I kept a list of the items as a flat file. The process at that time was quite crude because I was not familiar yet with the power of SYNCSORT. The list of items had the source PDS, the member. Based on the PDS name, the job will generate JCL to perform other functions.For example, if it was a SYSIN card, then the generated job will copy the member from source PDS to target PDS using IEBCOPY. If it was a source, the generated job will copy the source, copy the Loadlib member, copy the compile listing, and if it was a DB2 program, copy the DBRMlib member and do a BIND Package.