| Author |
Message
|
| fredla |
 Posted: Wed Mar 30, 2005 11:18 pm Post subject: [solved]Import and Export FDL Files in Buildtime |
 |
|
Novice
Joined: 17 Mar 2005
Posts: 16
|
Can it be done in command line?
Just like that for runtime (fmcibie)
Last edited by fredla on Thu Mar 31, 2005 6:09 pm; edited 1 time in total |
|
| Back to top |
|
 |
| kotha |
| Posted: Thu Mar 31, 2005 6:12 am Post subject: |
|
|
Partisan
Joined: 12 Mar 2005
Posts: 333
|
| I dont think so. I didnt read anywhere about it. |
|
| Back to top |
|
|
| jmac |
| Posted: Thu Mar 31, 2005 6:37 am Post subject: Re: Import and Export FDL Files in Buildtime |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
| fredla wrote: |
Can it be done in command line?
|
YES
| kotha wrote: |
| I dont think so. I didnt read anywhere about it |
That's because it's not documented. 
Here are the commands:
| Code: |
fmcbcimp -?
Usage fmcbcimp [-option [argument] ... ]
If User ID and password are not specified, unified logon is carried out
If -y Configuration identifier is not specified, the default is used
If -b ODBCName is not specified, the configuration database is taken
If -i Filename is not specified, fmczrf31.fdl is imported
Logon
-u string User ID
-p string Password
Configuration and Database
-y string Configuration identifier
-b ODBCname ODBCName of database
-j string Database User ID
-w string Database Password
Import
-i filename FDL file name for import
-o Overwrite
-r From Runtime
Logging
-l [filename] Log file name
(file name will be generated)
Example:
fmcbcimp /uADMIN /pPASSWORD /iTEST.FDL /lIMPORT.LOG /o /yMYCFG |
| Code: |
C:\>fmcbcexp -?
Usage fmcbcexp [-option [argument] ... ]
If user ID and password are not specified, unified logon is carried out
If -y Configuration identifier is not specified, therefore, the default is used
If -b ODBCName is not specified, therefore, the configuration database is taken
If -c Command string is not specified, therefore, all objects in Buildtime are exported
Logon
-u string User ID
-p string Password
Configuration and Database
-y string Configuration identifier
-b ODBCname ODBCName of database
-j string Database user ID
-w string Database password
Export
-c string Commands or @filename
-e filename FDL file name for export
-d Deep
Logging
-l [filename] log file name
(file name will be generated)
Example:
fmcbcexp /uADMIN /pPASSWORD /eTEST.FDL /lEXPORT.LOG /c@input /yMYCFG |
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| praveenchhangani |
| Posted: Thu Mar 31, 2005 6:42 am Post subject: |
|
|
Disciple
Joined: 20 Sep 2002
Posts: 192
Location: Chicago, IL
|
I might simply add by saying that these commands will only run on the Windows environment.
_________________
Praveen K. Chhangani,
IBM Certified Solutions Designer -
MQ Workflow 3.4. |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Thu Mar 31, 2005 8:03 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
| May be I am wrong. Do we have any other version of Buildtime other than on Windows? Probably Linux |
|
| Back to top |
|
|
| jmac |
| Posted: Thu Mar 31, 2005 8:06 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
From the Installation Guide:
Buildtime requirements
Although the Buildtime tool itself only runs on Windows machines, the Buildtime database does not have to be on Windows. You can host the Buildtime database on a remote UNIX machine.
As of 3.5 Buildtime is a Windows only component of MQWF.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| fredla |
| Posted: Thu Mar 31, 2005 6:08 pm Post subject: |
|
|
Novice
Joined: 17 Mar 2005
Posts: 16
|
|
| Back to top |
|
|
|
|
