It can also be used to dump the names of the exposures in a POD file.

If the input pod file contains a newline (\n) character every 513th byte, these will be omitted from the output pod file.  This corrects a problem where some pod files were archived with VMS carriage control added in.

This is designed only for the DDF POD files which begin with the 0x3A in the first byte (STIS, NIC, ACS).
 

        %podwhacker [-f] {podfile_name}
                [-list {exposure_name_list}]
                [-names {comma_delimited_list_of_expnames}]

                [-o {output_file_name}]

 

Inputs

[-f] {podfile_name}
This is the fully qualified name of the input POD file. It can be in any path.  The -f specifier is optional.
-names {comma_delimited_list_of_expnames}
The comma_delimited_list_of_expnames is a comma-delimited list of exposure names WITH NO SEPARATING BLANKS. Thus you can specify a single exposure with -n N43Q1412Q, or a few exposures:

-n N43Q1412Q,N43Q1413Q,N43Q1414Q

If you have more than a few exposures to extract, use the -list option below instead.
If not specified this argument pair defaults to "-n zzz" which results in a listing of exposures.
 
-list {exposure_name_list}
The exposure_name_list is the name of a file which contains the list of exposures which you want extracted from the POD file. You should put one exposure name per line in that file.


-o {output_file_name}
        The output pod file name.  If this is not specified, then the output pod file name will be formed by altering the 15th character of the input file name or the last character of the input file name if it is less than 15 characters long.  The character will be altered to 's' if possible, or if the input file already has 's' in the 15th character then 't' will be used.  This progress goes on using 'u', 'v', etc. until a unique output file name can be formed.

Each time the task encounters another exposure it will print a message to stderr (usually the screen). The output .POD file is created in your current working directory. The name of this file is selected by the -o option or determined automatically (see the -o option description above).
 
 

        %podwhacker lz_7e9d1997091409561073.pod -n N44T01LUQ
        %podwhacker lz_7e9d1997091409561073.pod -list my_exposures.lis
        %podwhacker lz_7e9d1997091409561073.pod -name N44T01LUQ,N44T01LVQ

The first invocation below finds out what ipppsoots are in the .pod file:

$ podwhacker DISK$ZETA:[DPT_PODS.NICMOS]LZ_7E9D1997091409561073.POD;1 
opened: lz_7e9d1997091s09561073.pod
qac_start=1618262, end_of_file=1618270
found: N44T01LUQ
found: N44T01LUQ
found: N44T01LUQ
found: N44T01LUQ
found: N44T01LUQ
found: N44T01LUQ
found: N44T01LUQ
found: N44T01LUQ
found: N44T01LUQ
found: N44T01LUQ
found: N44T01LUQ
found: N44T01LUQ
found: N44T01LUQ
found: N44T01LVQ
found: N44T01LVQ
found: N44T01LVQ
found: N44T01LVQ
found: N44T01LVQ
found: N44T01LVQ
found: N44T01LVQ
found: N44T01LVQ
found: N44T01LVQ
found: N44T01LVQ
found: N44T01LVQ

The second invocation actually extracts N44T01LUQ

$ podwhacker DISK$ZETA:[DPT_PODS.NICMOS]LZ_7E9D1997091409561073.POD;1 -n N44T01LUQ
opened: lz_7e9d1997091s09561073.pod
qac_start=1618262, end_of_file=1618270
found: N44T01LUQ, saving it
found: N44T01LUQ, saving it
found: N44T01LUQ, saving it
found: N44T01LUQ, saving it
found: N44T01LUQ, saving it
found: N44T01LUQ, saving it
found: N44T01LUQ, saving it
found: N44T01LUQ, saving it
found: N44T01LUQ, saving it
found: N44T01LUQ, saving it
found: N44T01LUQ, saving it
found: N44T01LUQ, saving it
found: N44T01LVQ
found: N44T01LVQ
found: N44T01LVQ
found: N44T01LVQ
found: N44T01LVQ
found: N44T01LVQ
found: N44T01LVQ
found: N44T01LVQ
found: N44T01LVQ
found: N44T01LVQ
found: N44T01LVQ

$ dir lz*

Directory DISK$LEO:[LEO.ROSE.SRC]

LZ_7E9D1997091S09561073.POD;2           LZ_7E9D1997091S09561073.POD;1

Total of 2 files.