Difference between revisions of "ISeries 101"
From MidrangeWiki
(→Multi User Queue Theory) |
m |
||
| (9 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
[[Category:Administration]] | [[Category:Administration]] | ||
| − | People who move to the 400 from other computing environments and backgrounds have some common areas of misconceptions and concepts difficult to grasp at first. | + | [[Category:Basics 101]] |
| + | * People who move to the 400 from other computing environments and backgrounds have some common areas of misconceptions and concepts difficult to grasp at first. | ||
| + | * Also see [[400 Print 101]] terminology. | ||
| + | * Understanding these problem areas can assist HELP DESK personnel grasp the roots of some personnel problems. | ||
== Multi User Queue Theory == | == Multi User Queue Theory == | ||
| Line 10: | Line 13: | ||
== Compiled Objects == | == Compiled Objects == | ||
| + | |||
| + | Many users come from a PC environment that makes heavy use of scripted and interpretive languages that read a line of code and execute it. For such individuals, compiled programs can be a foreign concept. | ||
| + | |||
== Non-executable files == | == Non-executable files == | ||
| + | |||
| + | In much of PC world, concept of programs and data files is alien. Any PC file can be executed ... what it does depends on the 3 letter suffix after the dot at end of name. | ||
| + | |||
| + | In the 400 world, there are files that can be processed, compiled programs that process them, and source code from which the compiled objects were generated. | ||
| + | |||
| + | == External File Definitions == | ||
== Formats == | == Formats == | ||
| + | |||
| + | * Every file has at least one format. | ||
| + | * This is the layout of fields (columns of table). | ||
| + | * Not all programming languages support the concept of a file having more than one format. | ||
| + | |||
== Members == | == Members == | ||
| + | * Almost everything on 400 is an object. | ||
| + | * All objects are in a Library. | ||
| + | * All 400 Libraries are in a root [[QSYS]] Library. | ||
| + | * Files and other objects are in Libraries. | ||
| + | * Files can have more than one Format Layout. All files have at least one format. | ||
| + | * [[Members]] are in [[Files]]. All files have at least one Member. | ||
| + | * Records are in [[Members]]. Each row of a table is another name for a Record. | ||
| + | * Each column of a table is another name for a field of a format layout of a file. | ||
| + | |||
| + | === Source === | ||
| + | * Files in [[Libraries]] | ||
| + | * Software [[source]] in File by type of programming language. | ||
| + | * Each member is a different [[program]] or [[module]]. | ||
| + | * Each line of the member is a line of code for the program. | ||
| + | |||
| + | === Data === | ||
| + | * Files in Libraries | ||
| + | * Each File format is different layout of data in that file. | ||
| + | * Each member is different collection of data in that file. | ||
| + | |||
| + | ==== [[BPCS]] Examples ==== | ||
| + | |||
| + | * Labor Tickets History ends up in file FLT which has member FLT for the main data and member WORK for input batch that if all goes well will end up in member FLT. WORK uses the same format layout as FLT but the data stays separate until all validation completed on the new input. | ||
| + | * Customer data uses the same format layout for | ||
| + | ** Customer Orders | ||
| + | ** Return of Material from Customers | ||
| + | ** Quotes | ||
| + | ** Input work not yet finished keying | ||
| + | * Each of these scenarios use the same format file layout but the actual data in a different member. | ||
Latest revision as of 21:24, 9 September 2006
- People who move to the 400 from other computing environments and backgrounds have some common areas of misconceptions and concepts difficult to grasp at first.
- Also see 400 Print 101 terminology.
- Understanding these problem areas can assist HELP DESK personnel grasp the roots of some personnel problems.
Contents
Multi User Queue Theory
Many users come to the 400 from a Desk Top reality where they were the only people using some computing resource. Such people can have trouble comprehending
- a multi-user environment in which
- Jobs can go to JOBQ to not run right away, but send Message to MSGQ upon completion;
- Reports to Printer OUTQ wait in line behind other people's reports;
- Reports from multiple people can be accessed.
Compiled Objects
Many users come from a PC environment that makes heavy use of scripted and interpretive languages that read a line of code and execute it. For such individuals, compiled programs can be a foreign concept.
Non-executable files
In much of PC world, concept of programs and data files is alien. Any PC file can be executed ... what it does depends on the 3 letter suffix after the dot at end of name.
In the 400 world, there are files that can be processed, compiled programs that process them, and source code from which the compiled objects were generated.
External File Definitions
Formats
- Every file has at least one format.
- This is the layout of fields (columns of table).
- Not all programming languages support the concept of a file having more than one format.
Members
- Almost everything on 400 is an object.
- All objects are in a Library.
- All 400 Libraries are in a root QSYS Library.
- Files and other objects are in Libraries.
- Files can have more than one Format Layout. All files have at least one format.
- Members are in Files. All files have at least one Member.
- Records are in Members. Each row of a table is another name for a Record.
- Each column of a table is another name for a field of a format layout of a file.
Source
- Files in Libraries
- Software source in File by type of programming language.
- Each member is a different program or module.
- Each line of the member is a line of code for the program.
Data
- Files in Libraries
- Each File format is different layout of data in that file.
- Each member is different collection of data in that file.
BPCS Examples
- Labor Tickets History ends up in file FLT which has member FLT for the main data and member WORK for input batch that if all goes well will end up in member FLT. WORK uses the same format layout as FLT but the data stays separate until all validation completed on the new input.
- Customer data uses the same format layout for
- Customer Orders
- Return of Material from Customers
- Quotes
- Input work not yet finished keying
- Each of these scenarios use the same format file layout but the actual data in a different member.
