Packed-Decimal Numbers
Test Case and Physical Structure
|
 |
| |
Table of Contents |
v-22.08.30 - tcprev02.htm |
|
|
Introduction
The 1st objective of this Test Case is to describe and demonstrate how a person with a Windows or Linux system may download a data file from an IBM Mainframe System and then prepare the file format and file content to be easily accessed using spread sheet software or a Relational Data Base Management System.
The 2nd objective of this Test Case is to describe and demonstrate how a person with a Windows or Linux system may make a change to the new file using the spread sheet software and reverse the process by preparing the spread sheet file to be uploaded to an IBM Mainframe System.
The 3rd objective of this Test Case is to describe and demonstrate how to compare the file content of the original EBCDIC-encoded Mainframe file with the newly created EBCDIC-encoded file and review the results.
This Test Case uses job scripts and COBOL Programs to display the physical content of numeric values that are stored in a Packed-Decimal format or text strings that use ASCII or EBCDIC encoding schemas.
|
1.1.
|
Convert a File that was created on an IBM Mainframe to a File that may be easily imported into a Relational Data Base Management System (RDBMS) or spread sheet software such as Excel on Windows or LibreCALC on Linux.
|
|
1.2.
|
Access to production files on the IBM Mainframe should be "read-only" and limited to pre-defined security restrictions.
|
|
2.1.
|
Convert the EBCDIC-encoded Text Strings to ASCII.
|
|
2.2.
|
Convert the Packed-Decimal numeric strings to Zoned-Decimal with a leading sign symbol.
|
|
3.
|
Understanding the User Data
|
|
3.1.
|
Describe the Techniques and Tools available for users, support personnel and Developers to better understand the structure of the data and how to review the results of the steps within the data processing cycle.
|
|
3.1.1.
|
Develop a better understanding of the structure of the user data.
|
|
3.1.2.
|
Review how the data processing cycles impact the user data.
|
|
4.
|
This document was created and is maintained by SimoTime Technologies and Services. If you have any questions, suggestions, comments or feedback please use the following contact information.
|
|
4.1.
|
Send an e-mail to our helpdesk.
helpdesk@simotime.com
|
|
4.2.
|
Our telephone numbers are as follows.
1 415 763-9430 office-helpdesk
1 415 827-7045 mobile
|
We have made a significant effort to ensure the documents and software technologies are correct and accurate. We reserve the right to make changes without notice at any time. The function delivered in this version is based upon the enhancement requests from a specific group of users. The intent is to provide changes as the need arises and in a timeframe that is dependent upon the availability of resources.
Copyright © 1987-2022
SimoTime Technologies and Services
All Rights Reserved
Understand the User Data
The primary input data for this test case is an EBCDIC-encoded Record Sequential (RSEQ) file that has been downloaded from an IBM Mainframe System. The record structure for this file is defined in a COBOL Copy File.
Note: This document will use an outline format to describe the sequence of events for the various data management tasks. If the "Level Number" if highlighted the hyperlink will use the current Web Site location. If a link is embedded in the "text string" of the outline then the hyperlink will attempt to connect to the SIMOTIME Web Site.
|
1.
|
Primary Input File - This file was downloaded from an IBM Mainframe. The File Transfer Protocol (FTP) Utility program was used in "BINARY" mode. The file format is Record Sequential (RSEQ) and has a fixed record length of 80 bytes. The record structure is a group of concatenated data strings containing numeric values stored in a Packed-Decimal format and EBCDIC-encoded text strings.
|
|
1.2.
|
Review the File contents, this job script will show the file content for the EBCDIC Input file and the ASCII Output file.
|
|
1.2.1.
|
Review EBCDIC File content, this job script will present each record using hexadecimal notation. This will allow the user to determine the binary structure of the data. This can be very helpful when a file contains numeric values that are stored in a Binary, Packed-Decimal or Zoned-Decimal format.
|
|
1.2.2.
|
Review ASCII File content, this job script will present each record using hexadecimal notation. This will allow the user to determine the binary structure of the data. This can be very helpful when a file contains numeric values that are stored in a Binary, Packed-Decimal or Zoned-Decimal format.
|
Execute and Observe
Prepare, describe and demonstrate the techniques used to share data across a network that includes a variety of systems such as IBM Mainframes, IBM i-series (AS/400), Windows Systems, UNIX Systems and Linux Systems.
The following describes the process of executing a test case that will start with an EBCDIC-encoded file that has been downloaded from an IBM Mainframe System. The process will start by converting the EBCDIC-encoded file to an ASCII-encoded file. The process will finish by creating an ASCII-encoded, Line Sequential (LCSV) file with a record structure that uses a Comma Separated Values (CSV) format. The Packed-Decimal strings will be converted to Zoned-Decimal with a separate leading sign character.
|
1.
|
Convert EBCDIC to ASCII - Execute a user defined job script that will define the environment and convert and EBCDIC-encoded, Record Sequential File to an ASCII-encoded, Record Sequential file. The integrity of the numeric values stored in a packed-Decimal format will be maintained.
|
|
1.1.
|
View the Content of the Job Script - this Job Script that will run a COBOL program to Convert EBCDIC to ASCII and show the results.
|
|
1.1.1.
|
Review EBCDIC File, this job script will present each record using hexadecimal notation. This will allow the user to determine the binary structure of the data. This can be very helpful when a file contains numeric values that are stored in a Binary, Packed-Decimal or Zoned-Decimal format.
|
|
1.1.2.
|
Review ASCII File, this job script will present each record using hexadecimal notation. This will allow the user to determine the binary structure of the data. This can be very helpful when a file contains numeric values that are stored in a Binary, Packed-Decimal or Zoned-Decimal format.
|
|
2.
|
Expand Packed-Decimal - Execute a user defined job script that will define the environment and convert an ASCII-encoded, Record Sequential File to an ASCII-encoded, Line Sequential (LCSV) file with a record structure that uses a Comma Separated Values (CSV) format. The Packed-Decimal strings will be converted (or expanded) to Zoned-Decimal with a separate leading sign character.
|
|
2.1.
|
View the Content of the Job Script - this Job Script will Expand Packed Decimal numeric values to a Zoned-Decimal format with a separate Leading Sign character.
|
|
2.1.2.
|
Note: Subsequent processing by this test case will use this file in a programatic compare processs. Making a change to this file will cause a NOT Equal condition to occur. It may be helpful to see this result before encountering it in a real problem determination situation.
|
This completes the 1st objective for this test case.
Reverse the Process
This section will reverse the processing tasks discussed in the previous section of this document.
The following describes the process of executing a test case that will start with an ASCII-encoded Line Sequential file containing a record structure that uses a Comma-Separated-Values (LCSV) format to an ASCII-encoded, Record Sequential file (RSEQ) containing a record structure of concatenated fields. The process will finiish by converting the ASCII-encoded Record Sequential file to an ASCII-encode Record Sequential file.
|
1.
|
Convert spread sheet file - Execute a user defined job script that will define the environment and convert an ASCII-encoded Line Sequential file containing a record structure that uses a Comma-Separated-Values (LCSV) format to an ASCII-encoded, Record Sequential file (RSEQ) containing a record structure of concatenated fields. The concatenated fields may contain numeric values stored in a Packed-Decimal format and text strings.
|
|
1.1.
|
View the Content of the Job Script - this Job Script will do the Import by Field and convert the numeric values stored in a Zoned-Decimal format to a Packed-Decimal format.
|
|
2.
|
Convert ASCII to EBCDIC - Execute a user defined job script that will define the environment and convert an ASCII-encoded, Record Sequential file to an EBCDIC-encoded, Record Sequential File. The integrity of the numeric values stored in a packed-Decimal format will be maintained.
|
This completes the 2nd objective for this test case.
Validation and Support
The following will discuss come of the secondary functions included in this test case.
The following describes the process of executing a process that will start with an ASCII-encoded file that is maintained using spread sheet software. The process will end by creating an EBCDIC-encoded Record Sequential file containing a record structure of concatenated fields. The concatenated fields may contain numeric values stored in a Packed-Decimal format and text strings.
|
1.
|
Compare Two Files - Execute a job script that will define the environment and compare the content of two EBCDIC-encoded Record Sequential files. The record structure may be a single strings of data or a group of concatenated fields. The concatenated fields may contain numeric values that are stored in a Packed-Decimal format and text strings.
|
This completes the 3rd objective for this test case.
Reference Material
This section provides subject information about data structures and processing techniques used in this test case.
Review Packed-Decimal Format
Define a Packed-Decimal string using the following COBOL statements.The 1st statement is a comment (* is position 7) and is used to identify the relative byte position within the COBOL statement. The 2nd statement is a comment and is used to show a fully coded definition of a Packed-Decimal field. The 3rd statement actually defines a Packed-Decimal field using the abbreviated format.
....:.*..1....:....2....:....3....:....4....:....5....:....6....:....7....:....8
*01 NBR-STRING PIC S9(5) USAGE IS COMPUTATIONAL-3 VALUE 12345.
01 NBR-STRING PIC S9(5) COMP-3 VALUE 12345.
|
1.
|
Review the COBOL statement.
|
|
1.1.
|
The NBR-STRING defines the name of the string.
|
|
1.2.
|
The PIC S9(5) defines the string as a signed numeric structure containing five (5) digits.
|
|
1.3.
|
The COMP-3 defines the string as a numeric value stored in a Packed-Decimal format.
|
|
1.4.
|
The VALUE places a numeric value of 12345 into the NBR-STRING that is defined as Packed-Decimal format.
|
|
2.
|
Review physical content of the Packed-Decimal string that stores five digits and a sign in three bytes. The first line of the following shows a position indicator
|
|
2.1.
|
....:....1....:....2....:....3....
135
24C
|
|
2.2.
|
The preceding two lines uses double line Hexadecimal Notation to display the physical content of the Packed-Decimal string.
|
Review Hexadecimal Notation
The term "string" is used to refer to a unit of data. A string of data may be a single byte or a concatenated string of bytes. For this test case a byte is a unit of data equal to 8 bits. A byte may be divided into two parts that are referred to as "nibbles". Bits 0-3 of a byte may be referred to as the 1st nibble. Bits 4-7 of a byte may be referred to as the 2nd nibble.
|
1.
|
The term "string" is used to refer to a unit of data. A string of data may be a single byte or a concatenated string of bytes.
Note: For the COBOL environment the term "FIELD" my be used instead of the term "STRING".
|
|
2.
|
For this test case a byte is a unit of data equal to 8 bits.
|
|
2.1.
|
Each bit is represented by a "0" for "OFF" or a "1" for "ON".
|
|
2.1.1.
|
010000001 01000010 01000011 would be the bit strings for the letters "ABC" for an ASCII encoded environment.
|
|
2.1.2.
|
110000001 11000010 11000011 would be the bit strings for the letters "ABC" for EBDIC encoded environment.
|
|
2.2.
|
A byte may be divided into two parts that are referred to as "nibbles".
|
|
2.2.1.
|
Bits 0-3 of a byte may be referred to as the 1st nibble.
|
|
2.2.2.
|
Bits 4 7 of a byte may be referred to as the 2nd nibble.
|
|
3.
|
When using Hexadecimal-Notation to present the content of memory or the content of a record within a file there are two (2) popular formats. Both formats will use two (2) bytes of hexadecimal notation to show the content of each single byte of user data.
|
|
3.1.
|
The single line format presents two bytes of hex-notation in a horizontal row for each single byte of user data.
|
|
3.1.1.
|
The following shows the content of a three byte user data string that contains the letters "ABC".
x'414243' is for the ASCII environment.
x'C1C2C3' is for the EBCDIC environment.
|
|
3.2.
|
The double line format presents two bytes of hex-notation in a vertical column for each single byte of user data.
|
|
3.2.1.
|
The following shows the content of a three byte user data string that contains the letters "ABC".
"444" is nibble one for the ASCII environment.
"123" is nibble two for the ASCII environment.
"CCC" is nibble one for the EBCDIC environment.
"123" is nibble two for the EBCDIC environment.
|
Technical Details
This section provides additional technical details about the program members and control files that are included in this test case.
Job Scripts
The following provides an overview of the batch job scripts used in this test case. Links are provided to view the content of a Job Member and the results produced when the job member is executed.
|
1.
|
TCPA2EW2, Convert ASC to EBC by Field - Execute a user defined job script that will define the environment and convert an ASCII-encoded, Record Sequential file to an EBCDIC-encoded, Record Sequential File. The concatenated fields may contain numeric values stored in a Packed-Decimal format and text strings.
|
|
1.1.
|
View the Content of the Job Script - this Job Script that will run a COBOL program to Convert EBCDIC to ASCII and show the results.
|
|
2.
|
TCPCPEW2, Compare Two Files - This job script that will define the environment and compare the content of two EBCDIC-encoded Record Sequential files. The record structure may be a single strings of data or a group of concatenated fields. The concatenated fields may contain numeric values that are stored in a Packed-Decimal format and text strings.
|
|
2.1.
|
View the Content of the Job Script - this Job Script will run a COBOL program to sthl:http://www.simotime.com/cmd_tcpcpew2.htm;Compare Two Files and show the results.
|
|
3.
|
TCPE2AW2, Convert EBC to ASC by Field - Execute a user defined job script that will define the environment and convert an EBCDIC-encoded, Record Sequential file to an ASCII-encoded, Record Sequential File. The concatenated fields may contain numeric values stored in a Packed-Decimal format and text strings.
|
|
4.
|
TCPEXTW2, Extract by Field - Execute a user defined job script that will define the environment and convert an ASCII-encoded, Record Sequential File to an ASCII-encoded, Line Sequential (LCSV) file with a record structure that uses a Comma Separated Values (CSV) format. The Packed-Decimal strings will be converted to Zoned-Decimal with a separate leading sign character.
|
|
4.1.
|
View the Content of the Job Script - this Job Script will Expand Packed Decimal numeric values to a Zoned-Decimal format with a separate Leading Sign character.
|
|
5.
|
TCPHX4W2, Review the File Contents, this job script will show the file content for the EBCDIC Input file and the ASCII Output file. The File Format for both files is Record Sequential with a fixed record length of 80 bytes. The record structure (or Format) is a group of concatenated data strings. This test case includes a COBOL Copy File that defines the record structure. The record content contains data string that contain numeric values that are stored in a Packed-Decimal format and text strings that may be ASCII or EBCDIC encoded.
|
|
5.2.
|
Review EBCDIC File content, this job script will present each record using hexadecimal notation. This will allow the user to determine the binary structure of the data. This can be very helpful when a file contains numeric values that are stored in a Binary, Packed-Decimal or Zoned-Decimal format.
|
|
5.3.
|
Review ASCII File content, this job script will present each record using hexadecimal notation. This will allow the user to determine the binary structure of the data. This can be very helpful when a file contains numeric values that are stored in a Binary, Packed-Decimal or Zoned-Decimal format.
|
|
6.
|
TCPIMPW2, Convert spread sheet file - Execute a user defined job script that will define the environment and convert an ASCII-encoded Line Sequential file containing a record structure that uses a Comma-Separated-Values (LCSV) format to an ASCII-encoded, Record Sequential file (RSEQ) containing a record structure of concatenated fields. The concatenated fields may contain numeric values stored in a Packed-Decimal format and text strings.
|
|
6.1.
|
View the Content of the Job Script - this Job Script will do the Import by Field and convert the numeric values stored in a Zoned-Decimal format to a Packed-Decimal format.
|
|
7.
|
TCPPEKW2, Review by Field the content of an ASC-encoded, Record Sequential file that contains numeric values tha are stored in a Packed-Decimal format and Text strings that contain alphanumeric data.
|
|
7.1.
|
View the Content of the Job Script - this Job Script will Review by Field the content of a Record Sequential (RSEQ) file based on the record structure as defined in a COBOL Copy file. The Textual content (using Display function) and Physical content (using Hex-Notation) will be written to the SYSOUT Device.
|
The preceding Job Scripts are designed to be maintained and executed in a testing environment that is separate from the productiion environment. Refer to the Comments or Feedback section of this document for additional information.
COBOL Programs
The COBOL programs used in this test case were generated using SimoTime Technologies.
Review Source Code
The following provides links for viewing the generated COBOL Source Code.
|
1.
|
Convert EBCDIC to ASCII - this set of programs will convert an EBCDIC-encoded, Record Sequential File to an ASCII-encoded, Record Sequential file. The integrity of the numeric values stored in a Packed-Decimal format will be maintained.
|
|
1.1.
|
Review I/O Program - this is the main program that will do the File Access and call a second program to do the record content conversion.
|
|
2.
|
Extract by Field - this set of programs will convert an ASCII-encoded, Record Sequential File to an ASCII-encoded, Line Sequential (LCSV) file with a record structure that uses a Comma Separated Values (CSV) format. The Packed-Decimal strings will be converted to Zoned-Decimal with a separate leading sign character.
|
|
2.1.
|
Review I/O Program - this is the main program that will do the File Access and call a second program to do the record format and record content conversion.
|
|
3.
|
Import by Field file - this set of programs will convert an ASCII-encoded Line Sequential file containing a record structure that uses a Comma-Separated-Values (LCSV) format to an ASCII-encoded, Record Sequential file (RSEQ) containing a record structure of concatenated fields. The concatenated fields may contain numeric values stored in a Packed-Decimal format and text strings.
|
|
3.1.
|
Review I/O Program - this is the main program that will do the File Format conversion from Line Sequential (LSEQ) to Record Sequential and call a second program to do the record format and record content conversion.
|
|
4.
|
Convert ASCII to EBCDIC - this set of programs will convert ad ASCII-encoded, Record Sequential File to an EBCDIC-encoded, Record Sequential file. The integrity of the numeric values stored in a Packed-Decimal format will be maintained.
|
|
4.1.
|
Review I/O Program - this is the main program that will do the File Access and call a second program to do the record content conversion.
|
|
5.
|
Compare Two Data Files - this set of programs will compare two EBCDIC-encoded, Record Sequential files.
|
|
5.1.
|
Review Compare Program - this is the main program that will do a Data Compare of two files. When a NOT EQUAL condition is found a second program is called to show the content of the records. The positions within the records that are not equal are identified.
|
|
6.
|
Hexadecimal Dump - this set of programs will access a user file and present the record content in a hex-dump format.
|
|
6.1.
|
Review Hexadecimal Dump Program - this is the main program that will access a user file and call a second program that will present the record content in a Hex-Dump Format along with a dislay of the possible ASCII and EBCDIC character tranlation.
|
Compiler Directives
The following (DIRS_OS390_EBC_BAT_HLASM.dir) is a sample directives file that may be used for the COBOL environment that is configured for an EBCDIC encoded schema.
DIALECT"OS390"
CHARSET"EBCDIC"
AMODE"24"
ASSIGN"EXTERNAL"
IDXFORMAT"8"
IBMCOMP
NOTRUNC
HOSTNUMMOVE
HOSTNUMCOMPARE
NOSIGN-FIXUP
HOSTARITHMETIC
CHECKNUM
NOOPTIONAL-FILE
NOHOSTFD
NOQUERY
SSRANGE
COBIDY
NOANIM
outdd"SYSOUT 121 L"
SHARE-OUTDD
DATE
TIME
DATAMAP
settings
list()
noform
Ancillary Functions
This section provides additional technical details about technologies that are external to this test case and are called to perform shared functions.
System and Job Environments
The following Windows Command(ENV1BASE.cmd) is the job script that sets the System environment variables.
Post Messages for Review
The following Windows Command(SIMONOTE.cmd) is the job script that is call from other job scripts to post user messages to the System Console and the device that is mapped to SYSOUT.
Summary
This Test Case uses a suite of job scripts and COBOL Programs to do file format and file content conversions. The results will be presented in a text format based on the encoding schema. The physical content of the records will be displayed using hexadecimal notation. This document may be used to assist as a tutorial for new programmers or as a quick reference for experienced programmers.
In the world of programming there are many ways to solve a problem. This documentation and software were developed and tested on systems that are configured for a SIMOTIME environment based on the hardware, operating systems, user requirements and security requirements. Therefore, adjustments may be needed to execute the jobs and programs when transferred to a system of a different architecture or configuration.
SIMOTIME Services has experience in moving or sharing data or application processing across a variety of systems. For additional information about SIMOTIME Services or Technologies please contact us using the information in the Contact, Comment or Feedback section of this document.
Software Agreement and Disclaimer
Permission to use, copy, modify and distribute this software, documentation or training material for any purpose requires a fee to be paid to SimoTime Technologies. Once the fee is received by SimoTime the latest version of the software, documentation or training material will be delivered and a license will be granted for use within an enterprise, provided the SimoTime copyright notice appear on all copies of the software. The SimoTime name or Logo may not be used in any advertising or publicity pertaining to the use of the software without the written permission of SimoTime Technologies.
SimoTime Technologies makes no warranty or representations about the suitability of the software, documentation or learning material for any purpose. It is provided "AS IS" without any expressed or implied warranty, including the implied warranties of merchantability, fitness for a particular purpose and non-infringement. SimoTime Technologies shall not be liable for any direct, indirect, special or consequential damages resulting from the loss of use, data or projects, whether in an action of contract or tort, arising out of or in connection with the use or performance of this software, documentation or training material.
Downloads and Links
This section includes links to documents with additional information that are beyond the scope and purpose of this document. The first sub-section requires an internet connection, the second sub-section references locally available documents.
Note: A SimoTime License is required for the items to be made available on a local server.
Current Server or Internet Access
The following links may be to the current server or to the Internet.
Explore The ASCII and EBCDIC Translation Tables. These tables are provided for individuals that need to better understand the bit structures and differences of the encoding formats.
Explore The File Status Return Codes to interpret the results of accessing VSAM data sets and/or QSAM files.
Internet Access Required
The following links will require an internet connect.
You may view the download list of the SimoTime shared modules at http://www.simotime.com/sim4dzip.htm#groupSHARED.
Explore
an Extended List of Software Technologies
that are available for review and evaluation. The software technologies (or Z-Packs) provide individual programming examples, documentation and test data files in a single package. The Z-Packs are usually in zip format to reduce the amount of time to download.
A good place to start is
The SimoTime Home Page
for access to white papers, program examples and product information. This link requires an Internet Connection
Explore
The Micro Focus Web Site
for more information about products (including Micro Focus COBOL) and services available from Micro Focus. This link requires an Internet Connection.
Explore
the GnuCOBOL Technologies
available from SourceForge. SourceForge is an Open Source community resource dedicated to helping open source projects be as successful as possible. GnuCOBOL (formerly OpenCOBOL) is a COBOL compiler with run time support. The compiler (cobc) translates COBOL source to executable using intermediate C, designated C compiler and linker. This link will require an Internet Connection.
Glossary of Terms
Explore the Glossary of Terms for a list of terms and definitions used in this suite of documents and white papers.
Comments or Feedback
This document was created and is maintained by SimoTime Technologies and Services. If you have any questions, suggestions, comments or feedback please use the following contact information.
|
1.
|
Send an e-mail to our helpdesk.
|
|
2.
|
Our telephone numbers are as follows.
|
|
2.1.
|
1 415 763-9430 office-helpdesk
|
|
2.2.
|
1 415 827-7045 mobile
|
We appreciate hearing from you.
Company Overview
SimoTime Technologies was founded in 1987 and is a privately owned company. We specialize in the creation and deployment of business applications using new or existing technologies and services. We have a team of individuals that understand the broad range of technologies being used in today's environments. Our customers include small businesses using Internet technologies to corporations using very large mainframe systems.
Quite often, to reach larger markets or provide a higher level of service to existing customers it requires the newer Internet technologies to work in a complementary manner with existing corporate mainframe systems. We specialize in preparing applications and the associated data that are currently residing on a single platform to be distributed across a variety of platforms.
Preparing the application programs will require the transfer of source members that will be compiled and deployed on the target platform. The data will need to be transferred between the systems and may need to be converted and validated at various stages within the process. SimoTime has the technology, services and experience to assist in the application and data management tasks involved with doing business in a multi-system environment.
Whether you want to use the Internet to expand into new market segments or as a delivery vehicle for existing business functions simply give us a call or check the web site at http://www.simotime.com
Copyright © 1987-2022
SimoTime Technologies and Services
All Rights Reserved |
| When technology complements business |
| http://www.simotime.com |