This utility converts a CGM file to a floating-point ADMGDF file.
If you simply want to display the file on screen, and if you are calling
it using ADMUCG, under CMS just enter:
ADMUCG cgmfilename
All other parameters are optional.
If you want to convert a CGM file to an ADMGDF file, the CGM filename,
filetype, and filemode, and the GDF filename are mandatory. For example,
under CMS:
ADMUCG cgmfilename cgmfiletype cgmfilemode gdffilename
The GDF filetype and filemode are optional.
Format
|
|
| CMS: |
| ADMUCG |
cgm-file gdf-file ( keyword_parms |
| TSO: |
| CALL |
'data_set_name(ADMUCG)' |
| |
'FROM(cgm-file) TO(gdf-file) keyword_parms' |
Under CMS, the keywords following the opening parenthesis can occur in any
order. If a keyword is specified more than once, the last specification
is used.
Under TSO, all of the keywords (including FROM and TO) can occur in any
order. If a keyword is specified more than once, the last specification
is used. The parameters following all of the keywords (including FROM and
TO) must be enclosed in parentheses.
Keywords: Permitted keywords with their parameters (with the minimum
abbreviation shown in uppercase) are:
PICture picture-number
PROFile profname
View
NEW | REPlace
Codepage cpn
- PICture
- The sequence number within the CGM of the picture to be
converted. Use -1 to choose all the pictures (the default).
- PROFile
- The name of the conversion profile to be used. If the profile
name is not specified, the default is ADM, except on CMS. On
CMS, the filetype of the CGM file is used as the profile name.
For example, on CMS:
ADMUCG MYCGM MYTYPE A MYADF ADMGDF A
would use a default profile name of MYTYPE. However, if the CGM
filetype is CGM, profile ADM is used (if found). Otherwise,
profile CGM is used.
On TSO, you must allocate DD name ADMCGM to point to your SADMSAM
data set to use the GDDM-supplied profiles, or to your own data
set if you want to use your own profile.
- View
- Displays the converted picture on the screen.
- NEW|REPlace
- Specifies how to deal with the output file.
- Codepage
- The code page that was used by the CGM generating application.
Parameters
- data_set_name
- The name of the data set containing the GDDM load library.
- cgm-file
- The input CGM file to be converted.
Under CMS, this parameter is a CMS fileid, as follows:
- fn
- The CMS filename of the file - any valid CMS file name.
- ft
- The CMS filetype of the file - any valid CMS file type. The
default is "CGM" (which GDDM maps onto the ADM profile). If
you use the appropriate conversion-profile name as the
filetype, GDDM uses that profile automatically for the
conversion and there is no need to specify it as a keyword.
- fm
- The CMS filemode of the file - any valid CMS file mode, or
"*" (default), indicating the first occurrence of the file in
the CMS search order.
Under TSO, this parameter specifies a fixed-block data set of
record length 400 containing the CGM file to be loaded. The
data set can be specified in one of the following ways:
- gdf-file
- The floating point ADMGDF file to be produced. If this
parameter is omitted, no output file is created and the VIEW
option is assumed.
Under CMS, this parameter is a CMS fileid, as follows:
- fn
- The CMS filename of the file - any valid CMS file name or
"=", indicating the same file name as the cgm-file.
- ft
- The CMS filetype of the file. This parameter is allowed but
ignored. The file type used is the current GDDM external
default value (usually "ADMGDF").
- fm
- The CMS filemode of the file. This can be omitted but must
be "A", if specified.
Under TSO, gdf-file is the name of a member within the
partitioned data set defined by the ddname ADMGDF or the GDDM
external default value. The new member created by this call to
ADMUCG must not exist already.
Description: The input CGM file is converted to GDF format and may be
viewed, saved in an ADMGDF file, or both. If the VIEW option is selected
or no output ADMGDF file is specified, the converted picture is shown on
the screen and a "read" is issued. Any PF key causes the VIEW function to
end, except for the key defined to invoke GDDM User Control. User Control
can be entered and the picture manipulated and saved in the usual way.
Manipulations have no effect on a picture subsequently saved as a GDF
file. Other keys such as CLEAR and the PA keys have their usual effect.
The permitted formats of the CGM files handled by this program are defined
in "CGM file format" in topic 13.4.
The CGM descriptors are handled in the following way:
- The text from the begin metafile and metafile descriptor elements of
the metafile are discarded.
- The name from the begin picture element is placed in the ADMGDF file
as the GDF descriptor, after appropriate code page translation as
defined in "National language code pages" in topic 13.5.
ADMUCG uses the picture_info_parms provided in the conversion profile (see
topic 13.6.2.1), except that a picture-number or cpn (code page number)
parameter will take precedence over the values in the profile.
Return codes
- 0
- Normal completion
- 100
- Too many (>6) name-parts: '(' not found when expected
- 101
- Invalid option: unexpected character string after '('
- 102
- Option value not numeric (CODEPAGE or PICTURE)
- 103
- Keyword >8 chars or value in ( ) too long (TSO only)
- 104
- CGLOAD failed
- 105
- GSSAVE failed
- 106
- ASREAD failed
- 107
- Specified GDF file filetype is not 'A'
- 108
- DSOPEN failed
- Other
- Return code from failed FSINIT or FSTERM.
|
GDDM V3R2 Base Application Programming Reference
Copyright IBM Corporation 1990, 2012