seedeploy: deploy configuration files and programs to a database or Azure Drive

Syntax

seedeploy [Options][Category]Action Parameters

Depending on the command's action, deploys, extracts, or deletes items in the region database, cross-region database, user-defined database, or an Azure Cloud drive (discussed in the Hosting CICS and Batch Applications in Windows Azure section). This includes:

  • Region startup files
  • Resource definition files
  • Programs (.dll files)
  • BMS Mapset files (.mod files)
  • Program symbols for debugging (.PDB files)
  • Data files, VSAM and fixed and line sequential file types.

Option parameter

For all actions, Option can have the following values:

Option
  • -nobanner

    Display minimal output, same as -quiet.

  • -quiet

    Display minimal output.

  • -urlhelp

    Display information about the URL syntax.

  • -verbose

    Display additional information in the list output.

Category parameter

The Category parameter defines the item to be acted upon. Valid values are:

  • binary

    The item acted upon is a binary file, for example a DLL file. This is the default.

  • rdo or resdef

    The item acted upon is a resource definition file.

  • regionfile

    The item acted upon is a region startup file.

  • clouddrive

    The action specified is to be done against an Azure cloud drive hosted in a monitor worker role, deployed into Azure.

  • Data

    The action acted upon is a VSAM, line sequential or fixed length sequential file.

Action parameter

The Action parameter defines the process performed on the specified item. It can have the following values. Each performs a specific function.

  • create

    Creates a table in a specified database. There is no create action for cloud drive operations.

  • add

    Deploys the specified file to the database or Azure cloud drive.

  • delete

    Deletes the specified item from the database or Azure cloud drive.

  • extract

    Copies the specified item from the database or Azure cloud drive to a file.

  • list

    Lists the contents of the specified database table or directory on an Azure cloud drive.

Refer to the See Also link at the end of this topic for information on defining a component's URL location.

create action 

seedeploy [Option][Category]create <url>

Creates a table in a database such as a cross-region database, a region database, or a user-defined database. If the specified database does not exist, the action creates a simple database and adds the table to it.

Note: This action is not supported with the rdo and regionfile category parameters, or for the data category with VSAM or sequential files.

create parameters

url
The name of the new or existing database in URL format.
name
The name of the table to create.

add action

Syntax:

  • For binary category: 
    seedeploy Option category add file  url[#name]
  • For rdo and regionfile categories: 
    seedeploy [option] [category] add file sql://host[/inst]/(crdb)/filename
  • For Azure cloud drive: 
    seedeploy [option] clouddrive  add file cdrv://host/FullFilePath
  • For Data category: 
    seedeploy [option] data  add file sql://host/[/inst]/datastore/filename?[folder=path][;type=type][;reclen=min,max]

Adds an item to the database or Azure cloud drive. You can use wildcards in the filename to add multiple files for database targets, but not currently for Azure cloud drives.

Note:
  • With binary files and cloud drive targets, first use the delete action to remove the old file.
  • With region startup and resource definition files, the add action overwrites the existing file. You do not need to remove the file first.

add parameters

file
The path and filename of the file to be loaded. Filenames can include wildcards to specify multiple files.
Url
See the section below on URL syntax.

delete action

Deletes the specified item in the region or cross-region database. If the name has an extension, for example ACCT01.DLL, this command deletes only the item with the matching name and file type. Otherwise, it deletes all matching items.

Syntax: 

seedeploy [Option] [category] delete url#name

delete parameters

URL

The item to delete's database location in URL format.

See the section below on URL syntax.

extract action

Extracts the contents of the specified item to a file. The name part of the URL must include the file type.

Syntax:

  • For binary category: 
    seedeploy [Option] [category] extract  url#name path
  • For rdo and regionfile categories: 
    seedeploy [option] [category] extract sql://host[/inst]/(crdb)/filename
  • for Azure cloud drive: 
    seedeploy [Option]  clouddrive extract  cdrv://host/FullFilePath file

extract parameters

path
The location and name of the file to hold the extracted data.
URL

The database location in URL format of the item to be extracted.

See the section below on URL syntax.

FullFilePath

The full path to the file to be extracted.

list action

Lists the contents of the specified table. Use the -verbose to display additional information.

Syntax: 

seedeploy [Option] [category] list url
Note: The list format is different for binary and rdo/ resdef resources. The -verbose option displays additional columns.

list parameters

URL

The database location in URL format of the item to be extracted.

See the section below on URL syntax.

Examples:

  • Create
    • The following command creates a new VSAM datastore in the database on the host\inst database server instance. 
      seedeploy data create sql://host/inst/VSAM
  • Add
    • The following command deploys the pgm.dll.old assembly to the db database on the host\inst database server instance. 
      seedeploy add pgm.dll.old sql://host/inst/db/Programs#pgm.dll
    • The following command deploys the resdef.config resource definition file to the cross-region database on the myhost\inst1 database server instance. 
      seedeploy rdo add c:\resourcedir\resdef.cfg sql://myhost/inst1/(crdb)
    • The following command deploys the regiondef.config region definition file to the installation's cross-region database on the myhost\inst1 database server instance:. 
      seedeploy regionfile add c:\regiondir\regiondef.config sql://myhost/inst1/(crdb)
    • The following command deploys a VSAM file employee.dat to a datastore on the myhost\inst1 database server instance:. 
      seedeploy data add c:\datadir\employee.dat sql://myhost/inst1/datastore/employee.dat?folder=VSAMFILES
    • The following command deploys a line sequential file employee.seq to a datastore on the myhost\inst1 database server instance:. 
      seedeploy data add c:\datadir\employee.seq sql://myhost/inst1/datastore/employee.seq?folder=SEQFILES;type=lseq;reclen=0,132
    • The following command deploys a fixed length sequential file employee1.seq to a datastore on the myhost\inst1 database server instance:. 
      seedeploy data add c:\datadir\employee1.seq sql://myhost/inst1/datastore/employee1.seq?folder=SEQFILES;type=seq;reclen=80,80
    • The following command deploys the acct.dll to an Azure drive configured as M: to a folder /programfolder/transactions. 
      seedeploy clouddrive add c:\transactions\acct.dll 
	             cdrv://example.cloudapp.net/m:/programfolder/transactions/acct.dll
  • Delete
    • The following command deletes ACCT00.DLL from the cross-region database. 
      seedeploy delete sql://localhost/(crdb)#ACCT00.DLL
    • The following command deletes all files starting with ACCT00, regardless of file type, for example ACCT00.DLL and ACCT00.PDB. 
      seedeploy delete sql://localhost/(crdb)#ACCT00
    • The following command deletes the resource definition file myResourceDef deployed to the cross-region database. 
      seedeploy rdo delete sql://localhost/(crdb)/myResourceDef>
    • The following command deletes ACCT00.DLL from the Azure cloud drive. 
      seedeploy clouddrive delete cdrv://example.cloudapp.net/m:/programfolder/transactions/ACCT00.DLL
  • Extract
    • The following command extracts the data from the row named pgm with the DLL file type, and saves it in the file pgm-from-db.dll in the current folder. 
      seedeploy extract sql://host/inst/db/Programs#pgm.dll pgm-from-db.dll
    • The following command extracts the resource definition file myResourceDefs.config from the cross-region database and saves it in the file resourcedef-from-db.config in the current folder. 
      seedeploy rdo extract sql://localhost/(crdb)/myResourceDefs resourcedef-from-db.config
    • The following command extracts the ACCT00.DLL file from the Azure cloud drive and saves it in the file ACCT00.DLL in the current folder. 
      seedeploy clouddrive extract cdrv://example.cloudapp.net/m:/programfolder/transactions/ACCT00.DLL .\ACCT00.DLL
  • List
    • The following command lists the contents of the Programs table in the SEEApps database on the local machine. 
      seedeploy list sql://localhost/SEEApps/Programs
    • The following command lists the resource definition files deployed to the cross-region database on the local machine. 
      seedeploy rdo list sql://localhost/ (crdb)
    • The following command lists the region startup files deployed to the cross-region database on the local machine. 
      seedeploy regionfile list sql://localhost/(crdb)
    • The following command lists the contents of the m:/programfolder/transactions folder on the Azure cloud drive. 
      seedeploy  clouddrive list cdrv://example.cloudapp.net/m:/programfolder/transactions

URL Syntax

SQL urls are constructed by placing a "sql://" or "cdrv://" followed by a mixture of the following syntax:

'clouddrive' category: cdrv://userid:password@servername/fullpath
  • userid - user login name as defined in monitor deployment setting
  • password - user password as defined in monitor deployment settings
  • Server - Name (may be "localhost")
  • fullpath - full pathname of file on Azure drive, e.g. m:\temp\testfile.dat
'binary' category: sql://server[/instance]/database/table[#key]
  • server - server hostname (may be "localhost")
  • instance - optional instance name
  • database - database name
  • table - table name
  • key - row primary key value

URLs for the "create" and "list" commands do not use keys.

URLs for other commands must have a key.

'rdo' category: sql://server[/instance]/database[/filename]

In the add command, a filename can be omitted, and the uploaded filename will be derived from the source filename.

  • server - server hostname (may be "localhost")
  • instance - optional instance name
  • database - database name. Must be '(crdb)' or '(crossRegionDatabase)'
  • filename - resource definition, region startup, or data file name

URLs for the "list" commands do not use filename.

URLs for other commands, except the data category, must have a filename.

'regionfile' category: sql://server[/instance]/database[/filename]

In the add command, a filename can be omitted, and the uploaded filename will be derived from the source filename

  • server - server hostname (may be "localhost")
  • instance - optional instance name
  • database - database name. Must be '(crdb)' or '(crossRegionDatabase)'
  • filename - resource definition, region startup, or data file name

URL's for the "list" commands do not use filename.

URL's for other commands, except the data category, must have a filename.

'data' category:

For an add, delete, or extract operation, the URL must take the form: sql://host[/instance]/datastore/filename[?folder=/path]

For a create or list operation, the URL must be of the form: sql://host[/instance]/datastore[?folder=/path]
  • server - server hostname (may be "localhost")
  • instance - optional instance name
  • datastore - datastore name
  • filename - resource definition, region startup, or data file name
  • path - name of folder to contain the file name in the datastore. It may have multiple parts. For example:
    • ...?folder=/MyDir
    • ...?folder=/MyDir/SubDir
  • For the add operation, the following attributes can be used:
    • type - the type of data object. Valid values are:
      • blob - blob types
      • lseq - line sequential file
      • seq - fixed length sequential file.
    • reclen - the min,max lengths of the sequential file.
      • ....;type-lseq;reclen=0,80

Example URLs:

  • sql://localhost/SEEApps/Programs
    • The table Programs in the database SEEApps, in the default instance on the local machine
  • sql://host/SQLEXPRESS/ACCT/Maps#ACCTSET
    • The binary with the key ACCTSET in the table ACCT in the instance SQLEXPRESS on host.
  • sql://localhost/SQLEXPRESS/(crdb)/ResourceDefinitions
    • The resource definition file with the name ResourceDefinitions in the cross-region database for the instance SQLEXPRESS on the local machine
  • sql://localhost/SQLEXPRESS/datastore/myseqfile?folder=/SEQFILES;type=seq;reclen=80,80
    • A fixed length 80 character per record, sequential file called myseqfile in folder /SEQFILES in a database called datastore
  • sql://localhost/SQLEXPRESS/datastore/myvsamfile?folder=/VSAM
    • A VSAM file called myvsamfile in the datastore database in a folder called VSAM
  • sql://localhost/SQLEXPRESS/binarystore/mytran.dll?folder=/applications;type=blob
    • A binary blob containing a dll called mytran.dll in a database called binarystore
  • cdrv://testuser:testpass@testhost.cloudapp.net/m:/programs/transact.dll
    • The transaction file called transact.dll in the programs directory on the azure drive mounted as m: in an azure deployment at testhost.cloudapp.net, using user id testuser and password testpass.

Special URLs:

Use e.g. "sql://server[/instance]/(regionDatabase)/ESDEMO/Programs" or "sql://server[/instance]/(rdb)/ESDEMO/Programs" for the Programs table in the ESDEMO region's region database.

Use "sql://host[/instance]/(crossRegionDatabase)" or"sql://host[/instance]/(crdb)" for the Binaries table in the cross-region database.

Parent topic: General Command Line Utilities