SecuritySNACCRuntime/doc/pval.1

   1 .\" Copyright (c) 1993 by Mike Sample and UBC
   2 .\" See section COPYING for conditions for redistribution
   3 .\" $Header: /cvs/root/Security/SecuritySNACCRuntime/doc/Attic/pval.1,v 1.1.1.1 2001/05/18 23:14:10 mb Exp $
   4 .\" $Log: pval.1,v $
   5 .\" Revision 1.1.1.1  2001/05/18 23:14:10  mb
   6 .\" Move from private repository to open source repository
   7 .\"
   8 .\" Revision 1.1.1.1  1999/03/16 18:05:54  aram
   9 .\" Originals from SMIME Free Library.
  10 .\"
  11 .\" Revision 1.2  1997/01/01 22:47:20  rj
  12 .\" first check-in
  13 .\"
  14 .TH PVAL 1 "11 July 1993"
  15 .SH NAME
  16 pval \- print BER values in ASN.1 value notation
  17 .SH SYNOPSIS
  18 .nf
  19 pval \-T <tt file name> [\-m <module name>] \-n <type name>
  20              <BER value file list>
  21 .SH DESCRIPTION
  22 pval prints the given BER values in their value notation.  You must
  23 specify the type name and optionally the module name of the type in
  24 the given BER files.
  25 .SH OPTIONS
  26 .TP
  27 .BI "\-T " file\c
  28 Use the type table in the file to look for the named types definition.
  29 .TP
  30 .BI "\-m " modulename\c
  31 Specifies the module in which the named type is defined.  If the
  32 module name is not specified with this option, pval looks for the
  33 first occurence of the named type in the modules in the given type
  34 table.
  35 .TP
  36 .BI "\-n " typename\c
  37 Specifies the type of the values in the given BER files.  If you
  38 give the wrong type name, decoding errors will occur.
  39 .PP
  40 .\" there is a tab between the file name and the description
  41 .SH FILES
  42 .PD 0
  43 .TP 28
  44 .B snacc/tbl-tools/pval/
  45 Source code for the pval program
  46 .SH COPYING
  47 Copyright (c) 1993 Mike Sample and the University of British Columbia
  48 .PP
  49 Permission is granted to make and distribute verbatim copies of
  50 this manual provided the copyright notice and this permission notice
  51 are preserved on all copies.
  52 .PP
  53 Permission is granted to copy and distribute modified versions of this
  54 manual under the conditions for verbatim copying, provided that the
  55 entire resulting derived work is distributed under the terms of a
  56 permission notice identical to this one.
  57 .PP
  58 .SH AUTHOR
  59 Mike Sample <msample@cs.ubc.ca>, University of British Columbia
  60 .SH ACKNOWLEDGEMENTS
  61 This work was made possible by grants from the Canadian Institute for
  62 Telecommunications Research (CITR) and Natural Sciences and
  63 Engineering Research Council of Canada (NSERC).