INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Jobs

Jobs from Indeed

Standard way to define types / lengths for columns in Mapper reports?

Standard way to define types / lengths for columns in Mapper reports?

Standard way to define types / lengths for columns in Mapper reports?

(OP)
Hi,

I'm a newbie to Mapper/BIS and trying to establish some documentation for Mapper reports, including a data dictionary. I've got what probably is a silly question about data types and columnar data in Mapper.

For example, you can define a variable, type and length in a RUN script using this syntax:

<myvar>i6

Is there an equivalent for defining data types and lengths of the columns defined by the column masks in an asterisk line? For example, if you have the asterisk and tab
lines below (to use an example Mapper report):

*OrdNo .Qty. Type     .Gender.
*======.===.==========.======.                        
   32001    1 Basketball  Mens    

Can you add an asterisk (or other) line below (or as part of) the column masks that defines the types of the column, i.e., something like this:

*i6----.i3-.a10-------.a6---.

Of course, you might be able to change RUN scripts to recognize and parse this kind of line, but I was wondering if there is a built-in, standard syntax or mechanism that Mapper recognizes. I've found that it would be nice if any piece code was a little more self-documenting, but I don't want to add anything to a report that would break a RUN.

Thanks for your help,
Alex
 

RE: Standard way to define types / lengths for columns in Mapper reports?

Alex
You could run the command RUN and then perform the manual commands. Once completed press F1 - Email me at yaw817@yahoo.com if you need additional assistance
Jay

RE: Standard way to define types / lengths for columns in Mapper reports?

Alex,

There was at one time a Unisys-supplied tool called APT that created and maintained a data dictionary and the cross-references. It lived in cab 214 on a 1100 system, or cab 14 on a Windows system.

There is also a run statement @dvs that creates variables based on the length of the field.

RE: Standard way to define types / lengths for columns in Mapper reports?

You can add an * line to your report with the field lengths if you want. But, if you do this, do not forget taht when enver you do various commands (Search) you must use the l(*) option. This will omit searching of the * line.

Also, when you do a RDL or RDC it is not required for you to put the lenght on the variable.


@rdl,100,i,90,6 'OrdNo','Qty','Type','Gender' <ordno>i,<qty>i,<type>a,<gender>a ,

Another way to fiend the lengths of the fields is to use the FCC command. Once you have the result on display, add it to the original report and do a REP.

RE: Standard way to define types / lengths for columns in Mapper reports?

Alex,
Now that you have been working with MAPPER/BIS for two months, what do you think of it?

RE: Standard way to define types / lengths for columns in Mapper reports?

I have two methods for documenting data in BIS/MAPPER.

*1*
Unisys supplies a utility called FCC that gives you Field Column Count like this:

CODE

.DATE   24 MAR 11  16:42:53     REPORT GENERATION   JERR      
.CABINET (0) DRAWER (D) REPORT (2) CHARACTERS (132)           
*Order   .Order   .Ship    .Customer.   .    .Product .      .
*Number  .Date    .Date    .Number  .Rep.Cat .Number  . Qty  .
*========.========.========.========.===.====.========.======.
 2-8      11-8     20-8     29-8     38-3     47-8     56-6   
                                         42-4                 
I don't like it for two reasons: (1) it overwrites the title that you had on line 2 and it does not show any data.  So I have my own DOCM routine that links to FCC (@LNK) and then produces output like this:

CODE

.DATE   24 MAR 11  16:45:03  RID    2D   23 AUG 10  JERR      
.CABINET (0) DRAWER (D) REPORT (-1) CHARACTERS (132)          
.Column-Formatted Data (PCME Demo Database)                   
*Order   .Order   .Ship    .Customer.   .    .Product .      .
*Number  .Date    .Date    .Number  .Rep.Cat .Number  . Qty  .
*========.========.========.========.===.====.========.======.
 2-8      11-8     20-8     29-8     38-3     47-8     56-6   
                                         42-4                 
|97156527|19970102|19970102|00000180|JIL|GAUZ|GAUZ0085|     9|
|97158918|19970102|19970102|00000246|MRP|ADBN|ADBN0002|    36|
|97159360|19970102|19970102|00000240|JIL|ANTI|ANTI0031|     4|
|97159839|19970102|19970102|00000164|MRP|COTT|COTT0019|    10|
|97159993|19970102|19970106|00000147|MRP|GAUZ|GAUZ0037|    27|
|97160433|19970102|19970102|00000204|MRP|FAKT|FAKT0040|    25|
If I have a rid that is wider than my paper, I use my WRAP routine to wrap the DOCM output to any width I specify.  I usually print this out and sit it next to my terminal as I work on runs.

*2*
---
PCEM (Point and Click MAPPER Enviroment) is a GUI interface to BIS provided by Unisys.  In PCME there is a subroutine in 55C that will take any rid as input and output a table that looks like this:

CODE

*Field                   .   .   .
*Name                    .Col.Siz.
*========================.===.===.
|St_Cd                   |  2|  2|
|Order_Number            |  5|  6|
|Product_Type            | 12|  9|
|Ord_Qty                 | 22|  3|
|Cust_Code               | 26|  4|
|Unit_Retail             | 31|  8|
|Extended_Retail         | 40|  8|
|Req d_Delivr            | 49|  6|
|Sale_Rep                | 56|  4|
|Customer                | 61| 17|
|Address                 | 79| 15|
|City                    | 95| 14|
|State                   |110|  5|
|Zip                     |116|  5|
All you need is run access to the PCME drawer:
@rnm,{anthing} -0 .
@call,3900,c,55 0001 () .
@dsp,-0 .

RE: Standard way to define types / lengths for columns in Mapper reports?

A few sites where I've worked have a standard that say, RID 1 of a drawer contains the data definition.  I have a little run called FLDS that can create a data definition from a RID - it's also callable and LNKable - I can upload it here if anyone wants a copy.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Resources

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close