Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

ASE 15.5 intallation from a resource file

6 posts in General Discussion Last posting was on 2012-01-04 11:10:21.0Z
Wilfredo Molina Posted on 2011-01-28 23:21:35.0Z
From: Wilfredo Molina <dwmolina@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; es-ES; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: ASE 15.5 intallation from a resource file
Content-Type: multipart/mixed; boundary="------------070803060605060605000906"
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4d434f7f$1@forums-1-dub>
Date: 28 Jan 2011 15:21:35 -0800
X-Trace: forums-1-dub 1296256895 10.22.241.152 (28 Jan 2011 15:21:35 -0800)
X-Original-Trace: 28 Jan 2011 15:21:35 -0800, vip152.sybase.com
Lines: 174
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:29904
Article PK: 79133

Hello,


I am attempting to install ASE 15.5 in silent mode from a resource file
but I am having some errors.

I attach the resource file sqlsrv.res

I executed the next line at command line and get the error "ERROR:The
property SYSAM_LICENSE_TYPE value is not specified or not valid." In the
next lines I get what are the optional values the SYSAM_LICENSE_TYPE
property should have. I added the SYSAM property to the resource file
but I still get the error. What can I do?
I didn't find too much documentation about creating resource files for
ASE 15.

_________________________________________________________________
C:\sybase>d:\ase1550_winx64_v2\setupConsole.exe -f C:\sybase\sqlsrv.res
-i silent
Preparing SILENT Mode Installation...

===============================================================================
Sybase Adaptive Server Enterprise Suite (created with
InstallAnywhere)
-------------------------------------------------------------------------------

ERROR:The property SYSAM_LICENSE_TYPE value is not specified or not valid.
The optional values for property SYSAM_LICENSE_TYPE:
CP : CPU License
SF : Standby CPU License
SR : Server License
SV : Standby Server License
DT : Development and Test License
EV : Evaluation License
OT : Other License
SS : Standalone Seat License
DV : Developer License
NA : Not Applicable or Other License
AC : OEM Application Deployment CPU License
BC : OEM Application Deployment Standby CPU License
AR : OEM Application Deployment Server License
BR : OEM Application Deployment Standby Server License
AO : OEM Application Deployment Other License
LP : Application Specific CPU License
LF : Application Specific Standby CPU License
LR : Application Specific Server License
LV : Application Specific Standby Server License
DH : Development and Testing Chip License
CH : Chip License
SH : Standby Chip License
AH : Application Deployment Chip License
BH : Application Deployment Standby Chip License
LH : Application Specific Chip License
LI : Application Specific Standby Chip License
Unknown
.



Thanks in advance,



--------------
Wilfredo Molina

AGREE_TO_SYBASE_LICENSE=true
RUN_SILENT=true
SYBASE_PRODUCT_LICENSE_TYPE=license
SYSAM_LICENSE_SOURCE=license_file
SYSAM_LICENSE_FILE_PATHNAME=C:\\sybase\\TheLicense.lic
SYSAM_PRODUCT_EDITION=Small Business Edition
SYSAM_LICENSE_TYPE=SR
#
# --- This file was generated by Sybase Installer ---
#
sybinit.boot_directory:C:\sybase
sybinit.release_directory:C:\sybase
sqlsrv.do_add_server:yes
sqlsrv.network_hostname_list:srvlnb11
sqlsrv.network_port_list:5000
sqlsrv.network_protocol_list:tcp
sqlsrv.notes:
sqlsrv.connect_retry_delay_time:5
sqlsrv.connect_retry_count:5
sqlsrv.new_config:yes
#
sqlsrv.server_name:CENTRAL_DS
sqlsrv.sa_password:
sqlsrv.sa_login:sa
sqlsrv.application_type:MIXED
sqlsrv.server_page_size:4k
#
# --- Set up master ----
#
sqlsrv.master_device_physical_name:E:\data\master_dd_1.dat
sqlsrv.master_device_size: 256
sqlsrv.master_db_size:128
sqlsrv.disk_mirror_name:
#
# --- Set up sybsystemprocs ----
#
sqlsrv.do_create_sybsystemprocs_device:yes
sqlsrv.sybsystemprocs_device_physical_name:E:\data\sysprocsdb_dd_1.dat
sqlsrv.sybsystemprocs_device_size:256
sqlsrv.sybsystemprocs_db_size:200
sqlsrv.sybsystemprocs_device_logical_name:sysprocsdb
#
# --- Set up sybsystemdb ----
#
sqlsrv.do_create_sybsystemdb:yes
sqlsrv.do_create_sybsystemdb_db_device:yes
sqlsrv.sybsystemdb_db_device_physical_name:E:\data\sybsysdb_dd_1.dat
sqlsrv.sybsystemdb_db_device_physical_size:64
sqlsrv.sybsystemdb_db_size:32
sqlsrv.sybsystemdb_db_device_logical_name:systemdb
sqlsrv.tempdb_device_physical_name:F:\data\tempdb_dd_1.dat
sqlsrv.tempdb_device_size:6144
sqlsrv.tempdb_database_size:6144
#
sqlsrv.errorlog:C:\sybase\ASE-15_0\install\CENTRAL_DS.log
sqlsrv.sort_order:binary
sqlsrv.default_characterset:iso885915
sqlsrv.default_language:us_english
#
sqlsrv.preupgrade_succeeded:no
sqlsrv.network_name_alias_list:
sqlsrv.resword_conflict:0
sqlsrv.resword_done:no
sqlsrv.do_upgrade:no
sqlsrv.characterset_install_list:
sqlsrv.characterset_remove_list:
sqlsrv.language_install_list:
sqlsrv.language_remove_list:
sqlsrv.shared_memory_directory:
sqlsrv.addl_cmdline_parameters:
sqlsrv.eventlog:yes
sqlsrv.atr_name_shutdown_required:yes
sqlsrv.atr_name_qinstall:no
#
sybinit.charset:iso885915
sybinit.language:us_english
sybinit.resource_file:
sybinit.log_file:
sybinit.product:sqlsrv
#
sqlsrv.default_backup_server:CENTRAL_DS_BS
#
sqlsrv.xpserver_network_protocol_list:tcp
sqlsrv.xpserver_network_hostname_list:srvlnb11
sqlsrv.xpserver_network_port_list:5003
#
sqlsrv.do_configure_pci:no
sqlsrv.sybpcidb_device_physical_name:
sqlsrv.sybpcidb_device_size:
sqlsrv.sybpcidb_database_size:
#
sqlsrv.do_optimize_config:no
sqlsrv.avail_physical_memory:
sqlsrv.avail_cpu_num:


"Mark A. Parsons" <iron_horse Posted on 2011-01-29 14:51:37.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: ASE 15.5 intallation from a resource file
References: <4d434f7f$1@forums-1-dub>
In-Reply-To: <4d434f7f$1@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4d442979$1@forums-1-dub>
Date: 29 Jan 2011 06:51:37 -0800
X-Trace: forums-1-dub 1296312697 10.22.241.152 (29 Jan 2011 06:51:37 -0800)
X-Original-Trace: 29 Jan 2011 06:51:37 -0800, vip152.sybase.com
Lines: 74
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:29905
Article PK: 79134

Where did you get your response file from? Did you run "setupConsole.exe -r" to generate your response file?

Do you get the same errors/issues if you use "setup.exe -f <response_file> -i silent"?

What are the PE and LT values from your license file (eg, "PE=DE;LT=DT")?

Agreed, it would be nice if Sybase supplied some sample response files for use with the setup(console) program.

On 01/28/2011 18:21, Wilfredo Molina wrote:
> Hello,
>
>
> I am attempting to install ASE 15.5 in silent mode from a resource file
> but I am having some errors.
>
> I attach the resource file sqlsrv.res
>
> I executed the next line at command line and get the error "ERROR:The
> property SYSAM_LICENSE_TYPE value is not specified or not valid." In the
> next lines I get what are the optional values the SYSAM_LICENSE_TYPE
> property should have. I added the SYSAM property to the resource file
> but I still get the error. What can I do?
> I didn't find too much documentation about creating resource files for
> ASE 15.
>
> _________________________________________________________________
> C:\sybase>d:\ase1550_winx64_v2\setupConsole.exe -f C:\sybase\sqlsrv.res
> -i silent
> Preparing SILENT Mode Installation...
>
> ===============================================================================
> Sybase Adaptive Server Enterprise Suite (created with
> InstallAnywhere)
> -------------------------------------------------------------------------------
>
> ERROR:The property SYSAM_LICENSE_TYPE value is not specified or not valid.
> The optional values for property SYSAM_LICENSE_TYPE:
> CP : CPU License
> SF : Standby CPU License
> SR : Server License
> SV : Standby Server License
> DT : Development and Test License
> EV : Evaluation License
> OT : Other License
> SS : Standalone Seat License
> DV : Developer License
> NA : Not Applicable or Other License
> AC : OEM Application Deployment CPU License
> BC : OEM Application Deployment Standby CPU License
> AR : OEM Application Deployment Server License
> BR : OEM Application Deployment Standby Server License
> AO : OEM Application Deployment Other License
> LP : Application Specific CPU License
> LF : Application Specific Standby CPU License
> LR : Application Specific Server License
> LV : Application Specific Standby Server License
> DH : Development and Testing Chip License
> CH : Chip License
> SH : Standby Chip License
> AH : Application Deployment Chip License
> BH : Application Deployment Standby Chip License
> LH : Application Specific Chip License
> LI : Application Specific Standby Chip License
> Unknown
> .
>
>
>
> Thanks in advance,
>
>
>
> --------------
> Wilfredo Molina


"Mark A. Parsons" <iron_horse Posted on 2011-01-30 18:36:11.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: ASE 15.5 intallation from a resource file
References: <4d434f7f$1@forums-1-dub>
In-Reply-To: <4d434f7f$1@forums-1-dub>
Content-Type: multipart/mixed; boundary="------------000602080005050102020706"
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4d45af9b$1@forums-1-dub>
Date: 30 Jan 2011 10:36:11 -0800
X-Trace: forums-1-dub 1296412571 10.22.241.152 (30 Jan 2011 10:36:11 -0800)
X-Original-Trace: 30 Jan 2011 10:36:11 -0800, vip152.sybase.com
Lines: 253
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:29906
Article PK: 79135

It's been a looooong time since I used a *response* file for installing the Sybase ASE software so I didn't want to say
anything until I created a ASE 15.5 *response* file myself ... but first some basics ...

------------------

Typically the first thing you need to do is install the Sybase ASE software.

You use the setup[console] program to do this.

You can perform this step in silent mode if you provide a *response* file. The caveat is that you must have a
*response* file, and as you've discovered Sybase does a lousy job of telling you what a *response* file looks like (and
I still haven't found a sample *response* file in the ASE 15.5 installation directory).

The only way (it seems) to determine the *response* file format is to do an initial run of the setup[console] program in
interactive mode and have it create a *response* file for you. Again, Sybase does a lousy job of documenting this (ie,
no concrete examples in the Install manual). I had to run the setupconsole program a couple times before I figured out
the format:

setupconsole -r <full_path_to_response_file>

eg: setupconsole -r N:\install\initial_response_file.txt

NOTE: For my initial try I provided just a filename, assuming the file would get created in the same directory where I
kicked off the setupconsole program. While the setupconsole program ran and successfully installed the ASE software and
configured an initial ASE dataserver, it did not create a *response* file (if it did create the file, I haven't been
able to locate it on my machine). So, make sure you provide a fully qualified path for the *response* file.

The output file will be in ascii text format. (For windows environments you may need to open with WordPad to get the
CR/LFs properly read.)

I've attached my *response* file [initial_response_file.txt].

------------------

Once the ASE software's been installed you can then look at creating your dataserver(s).

The setup[console] program gives you the option to setup an initial dataserver immediately after the ASE software has
been installed. If you run setup[console] in record mode (ie, create a *response* file), you'll see the dataserver
creation details in the later part of the *response* file (see my attached *response* file).

If you prefer to create a dataserver separate from the installation of the ASE software, then you can either go the
manual route and use the dataserver program (not recommended for newbies), or you can use the
srvbuild[res]/asecfg/sybatch/syconfig tools (depends on your OS). If you want to create a dataserver in silent mode
then you need to have a *resource* file, which is turn is fed to the srvbuildres/sybatch programs.

------------------

OK, now that we've got the basics out of the way ... and newbies are no doubt a tad bit confused ... we can look at your
post ...

The first item we need to address is terminology (per Sybase's definition).

A *response* file is used to install the ASE software (and if desired create an initial ASE dataserver). The *response*
file is created/used by the setup[console] programs.

A *resource* file is used, *after* the ASE software has been installed, to create a ASE dataserver. The *resource* file
is used by the srvbuildres/sybatch programs.

Next item is the format of these two files.

The *response* and *resource* files have different formats.

The file you attached to your post is formatted as a *resource* file, and has nothing to do with the installation of ASE
software. (I'm not sure why you added the 7 UNIX-like variable settings at the beginning of the file ... ??? I can't
say with 100% certainty that those variables are ignored ... but I don't recall ever seeing that kind of format in a
*resource* file ... ?)

Sybase does provide some sample *resource* files which you can normally find with a '.res' extension (buried somewhere
in your ASE software directory). ['.res' in Windows; not sure at the moment what the linux/unix extension looks like]

Again, Sybase doesn't seem to provide any *response* file samples so you're left having to perform an initial run of the
setup[console] program in record mode (-r).

------------------

Regarding those 7 UNIX-like variables settings ...

Those do look like entries from a *response* file. (see my attachment)

When I ran setupconsole I chose to install the developer version; my guess is that if you run setup[console] in record
mode (-r) that you'll find those UNIX-like variable settings (for Small Business/SR) show up in the *response* file
created by setup[console]. ("Duh, Mark!" ?)

On 01/28/2011 18:21, Wilfredo Molina wrote:
> Hello,
>
>
> I am attempting to install ASE 15.5 in silent mode from a resource file
> but I am having some errors.
>
> I attach the resource file sqlsrv.res
>
> I executed the next line at command line and get the error "ERROR:The
> property SYSAM_LICENSE_TYPE value is not specified or not valid." In the
> next lines I get what are the optional values the SYSAM_LICENSE_TYPE
> property should have. I added the SYSAM property to the resource file
> but I still get the error. What can I do?
> I didn't find too much documentation about creating resource files for
> ASE 15.
>
> _________________________________________________________________
> C:\sybase>d:\ase1550_winx64_v2\setupConsole.exe -f C:\sybase\sqlsrv.res
> -i silent
> Preparing SILENT Mode Installation...
>
> ===============================================================================
> Sybase Adaptive Server Enterprise Suite (created with
> InstallAnywhere)
> -------------------------------------------------------------------------------
>
> ERROR:The property SYSAM_LICENSE_TYPE value is not specified or not valid.
> The optional values for property SYSAM_LICENSE_TYPE:
> CP : CPU License
> SF : Standby CPU License
> SR : Server License
> SV : Standby Server License
> DT : Development and Test License
> EV : Evaluation License
> OT : Other License
> SS : Standalone Seat License
> DV : Developer License
> NA : Not Applicable or Other License
> AC : OEM Application Deployment CPU License
> BC : OEM Application Deployment Standby CPU License
> AR : OEM Application Deployment Server License
> BR : OEM Application Deployment Standby Server License
> AO : OEM Application Deployment Other License
> LP : Application Specific CPU License
> LF : Application Specific Standby CPU License
> LR : Application Specific Server License
> LV : Application Specific Standby Server License
> DH : Development and Testing Chip License
> CH : Chip License
> SH : Standby Chip License
> AH : Application Deployment Chip License
> BH : Application Deployment Standby Chip License
> LH : Application Specific Chip License
> LI : Application Specific Standby Chip License
> Unknown
> .
>
>
>
> Thanks in advance,
>
>
>
> --------------
> Wilfredo Molina

# Sun Jan 30 12:38:43 EST 2011
# Replay feature output
# ---------------------
# This file was built by the Replay feature of InstallAnywhere.
# It contains variables that were set by Panels, Consoles or Custom Code.



#Validate Response File
#----------------------
RUN_SILENT=true

#Choose Install Folder
#---------------------
USER_INSTALL_DIR=C:\\sybase

#Choose Install Set
#------------------
CHOSEN_FEATURE_LIST=fase_srv,fopen_client,fdblib,fjconnect60,fjconnect70,fodbcw,fado,fdbisql,fsc,fasep,fsysamp,famc,fsysam_util,fua,fase_agent
CHOSEN_INSTALL_FEATURE_LIST=fase_srv,fopen_client,fdblib,fjconnect60,fjconnect70,fodbcw,fado,fdbisql,fsc,fasep,fsysamp,famc,fsysam_util,fua,fase_agent
CHOSEN_INSTALL_SET=Custom

#Choose Product License Type
#---------------------------
SYBASE_PRODUCT_LICENSE_TYPE=developer

#Remember ASE Password
#---------------------
ASEP_REMEMBER_PASSWORD=FALSE
ASEP_REMEMBER_PASSWORD_1=
ASEP_REMEMBER_PASSWORD_2=Disable
ASEP_REMEMBER_PASSWORD_BOOLEAN_1=0
ASEP_REMEMBER_PASSWORD_BOOLEAN_2=1

#Configure New Servers
#---------------------
SY_CONFIG_ASE_SERVER=true
SY_CONFIG_BS_SERVER=true
SY_CONFIG_XP_SERVER=true
SY_CONFIG_JS_SERVER=false
SY_CONFIG_MS_SERVER=false
SY_CONFIG_SM_SERVER=false
SY_CONFIG_WS_SERVER=false
SY_CONFIG_UA_SERVER=false
SY_CONFIG_TXT_SERVER=false

#Configure New Adaptive Server
#-----------------------------
SY_CFG_ASE_SERVER_NAME=HP2
SY_CFG_ASE_PORT_NUMBER=5000
SY_CFG_ASE_APPL_TYPE=OLTP
SY_CFG_ASE_PAGESIZE=2k
SY_CFG_ASE_MASTER_DEV_NAME=O:\\Sybase\\devices\\HP2\\HP2_master.dat
SY_CFG_ASE_MASTER_DEV_SIZE=100
SY_CFG_ASE_MASTER_DB_SIZE=50
SY_CFG_ASE_SYBPROC_DEV_NAME=O:\\Sybase\\devices\\HP2\\HP2_sysprocs.dat
SY_CFG_ASE_SYBPROC_DEV_SIZE=200
SY_CFG_ASE_SYBPROC_DB_SIZE=200
SY_CFG_ASE_SYBTEMP_DEV_NAME=O:\\Sybase\\devices\\HP2\\HP2_sybsysdb.dat
SY_CFG_ASE_SYBTEMP_DEV_SIZE=10
SY_CFG_ASE_SYBTEMP_DB_SIZE=10
SY_CFG_ASE_ERROR_LOG=C:\\sybase\\ASE-15_0\\install\\HP2.log
SY_CFG_ASE_PCI_ENABLE=false
SY_CFG_ASE_PCI_DEV_NAME=$NULL$
SY_CFG_ASE_PCI_DEV_SIZE=$NULL$
SY_CFG_ASE_PCI_DB_SIZE=$NULL$
SY_CFG_ASE_TEMP_DEV_NAME=O:\\Sybase\\devices\\HP2\\HP2_tempdb_01.dat
SY_CFG_ASE_TEMP_DEV_SIZE=200
SY_CFG_ASE_TEMP_DB_SIZE=200
SY_CFG_ASE_OPT_ENABLE=true
SY_CFG_ASE_CPU_NUMBER=1
SY_CFG_ASE_MEMORY=500

#Configure New Backup Server
#---------------------------
SY_CFG_BS_SERVER_NAME=HP2_BS
SY_CFG_BS_PORT_NUMBER=5001
SY_CFG_BS_ERROR_LOG=C:\\sybase\\ASE-15_0\\install\\HP2_BS.log

#Configure New XP Server
#-----------------------
SY_CFG_XP_SERVER_NAME=HP2_XP
SY_CFG_XP_PORT_NUMBER=5002
SY_CFG_XP_ERROR_LOG=C:\\sybase\\ASE-15_0\\install\\HP2_XP.log


Wilfredo Molina Posted on 2011-01-31 18:06:05.0Z
From: Wilfredo Molina <dwmolina@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; es-ES; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: ASE 15.5 intallation from a resource file
References: <4d434f7f$1@forums-1-dub> <4d45af9b$1@forums-1-dub>
In-Reply-To: <4d45af9b$1@forums-1-dub>
Content-Type: multipart/mixed; boundary="------------080203010604010305090407"
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4d46fa0d@forums-1-dub>
Date: 31 Jan 2011 10:06:05 -0800
X-Trace: forums-1-dub 1296497165 10.22.241.152 (31 Jan 2011 10:06:05 -0800)
X-Original-Trace: 31 Jan 2011 10:06:05 -0800, vip152.sybase.com
Lines: 320
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:29908
Article PK: 79137

I am so grateful for your help Mark!

I think I got confused with the response and resource file.

Before I write to the group I run the setupConsole program with no full
path to a response file and I didn't find the response file anywhere as
you said.

But, as you write, with a full path I got the responsefile. Then I
executed the setupConsole programa to install ASE 15.5 completely in
silent mode without errors.

There was a little detail. I'm installing Sybase ASE 15.5 in Windows
Server 2008 with a windows account called sybase. I run the setupConsole
program in silent mode at command line but the typical authorization
window appeared because the sybase account isn't the SO Administrator.
So, I run a command line window as Administrator then executed the
setupConsole program in silent mode with the response file and the
installation was succesful.

Well, the problem that I wrote at first with the SYSAM_LICENSE_TYPE
property, was an incorrect value.

I've attached the response file I got from the setupConsole program in
record mode.





Thank you so much!


Excuse me for my writing. English isn't my primary language :)


El 30/01/2011 12:36 p.m., Mark A. Parsons escribió:

> It's been a looooong time since I used a *response* file for installing
> the Sybase ASE software so I didn't want to say anything until I created
> a ASE 15.5 *response* file myself ... but first some basics ...
>
> ------------------
>
> Typically the first thing you need to do is install the Sybase ASE
> software.
>
> You use the setup[console] program to do this.
>
> You can perform this step in silent mode if you provide a *response*
> file. The caveat is that you must have a *response* file, and as you've
> discovered Sybase does a lousy job of telling you what a *response* file
> looks like (and I still haven't found a sample *response* file in the
> ASE 15.5 installation directory).
>
> The only way (it seems) to determine the *response* file format is to do
> an initial run of the setup[console] program in interactive mode and
> have it create a *response* file for you. Again, Sybase does a lousy
> job of documenting this (ie, no concrete examples in the Install
> manual). I had to run the setupconsole program a couple times before I
> figured out the format:
>
> setupconsole -r <full_path_to_response_file>
>
> eg: setupconsole -r N:\install\initial_response_file.txt
>
> NOTE: For my initial try I provided just a filename, assuming the file
> would get created in the same directory where I kicked off the
> setupconsole program. While the setupconsole program ran and
> successfully installed the ASE software and configured an initial ASE
> dataserver, it did not create a *response* file (if it did create the
> file, I haven't been able to locate it on my machine). So, make sure
> you provide a fully qualified path for the *response* file.
>
> The output file will be in ascii text format. (For windows environments
> you may need to open with WordPad to get the CR/LFs properly read.)
>
> I've attached my *response* file [initial_response_file.txt].
>
> ------------------
>
> Once the ASE software's been installed you can then look at creating
> your dataserver(s).
>
> The setup[console] program gives you the option to setup an initial
> dataserver immediately after the ASE software has been installed. If
> you run setup[console] in record mode (ie, create a *response* file),
> you'll see the dataserver creation details in the later part of the
> *response* file (see my attached *response* file).
>
> If you prefer to create a dataserver separate from the installation of
> the ASE software, then you can either go the manual route and use the
> dataserver program (not recommended for newbies), or you can use the
> srvbuild[res]/asecfg/sybatch/syconfig tools (depends on your OS). If
> you want to create a dataserver in silent mode then you need to have a
> *resource* file, which is turn is fed to the srvbuildres/sybatch programs.
>
> ------------------
>
> OK, now that we've got the basics out of the way ... and newbies are no
> doubt a tad bit confused ... we can look at your post ...
>
> The first item we need to address is terminology (per Sybase's definition).
>
> A *response* file is used to install the ASE software (and if desired
> create an initial ASE dataserver). The *response* file is created/used
> by the setup[console] programs.
>
> A *resource* file is used, *after* the ASE software has been installed,
> to create a ASE dataserver. The *resource* file is used by the
> srvbuildres/sybatch programs.
>
> Next item is the format of these two files.
>
> The *response* and *resource* files have different formats.
>
> The file you attached to your post is formatted as a *resource* file,
> and has nothing to do with the installation of ASE software. (I'm not
> sure why you added the 7 UNIX-like variable settings at the beginning of
> the file ... ??? I can't say with 100% certainty that those variables
> are ignored ... but I don't recall ever seeing that kind of format in a
> *resource* file ... ?)
>
> Sybase does provide some sample *resource* files which you can normally
> find with a '.res' extension (buried somewhere in your ASE software
> directory). ['.res' in Windows; not sure at the moment what the
> linux/unix extension looks like]
>
> Again, Sybase doesn't seem to provide any *response* file samples so
> you're left having to perform an initial run of the setup[console]
> program in record mode (-r).
>
> ------------------
>
> Regarding those 7 UNIX-like variables settings ...
>
> Those do look like entries from a *response* file. (see my attachment)
>
> When I ran setupconsole I chose to install the developer version; my
> guess is that if you run setup[console] in record mode (-r) that you'll
> find those UNIX-like variable settings (for Small Business/SR) show up
> in the *response* file created by setup[console]. ("Duh, Mark!" ?)
>
>
>
>
>
>
> On 01/28/2011 18:21, Wilfredo Molina wrote:
>> Hello,
>>
>>
>> I am attempting to install ASE 15.5 in silent mode from a resource file
>> but I am having some errors.
>>
>> I attach the resource file sqlsrv.res
>>
>> I executed the next line at command line and get the error "ERROR:The
>> property SYSAM_LICENSE_TYPE value is not specified or not valid." In the
>> next lines I get what are the optional values the SYSAM_LICENSE_TYPE
>> property should have. I added the SYSAM property to the resource file
>> but I still get the error. What can I do?
>> I didn't find too much documentation about creating resource files for
>> ASE 15.
>>
>> _________________________________________________________________
>> C:\sybase>d:\ase1550_winx64_v2\setupConsole.exe -f C:\sybase\sqlsrv.res
>> -i silent
>> Preparing SILENT Mode Installation...
>>
>> ===============================================================================
>>
>> Sybase Adaptive Server Enterprise Suite (created with
>> InstallAnywhere)
>> -------------------------------------------------------------------------------
>>
>>
>> ERROR:The property SYSAM_LICENSE_TYPE value is not specified or not
>> valid.
>> The optional values for property SYSAM_LICENSE_TYPE:
>> CP : CPU License
>> SF : Standby CPU License
>> SR : Server License
>> SV : Standby Server License
>> DT : Development and Test License
>> EV : Evaluation License
>> OT : Other License
>> SS : Standalone Seat License
>> DV : Developer License
>> NA : Not Applicable or Other License
>> AC : OEM Application Deployment CPU License
>> BC : OEM Application Deployment Standby CPU License
>> AR : OEM Application Deployment Server License
>> BR : OEM Application Deployment Standby Server License
>> AO : OEM Application Deployment Other License
>> LP : Application Specific CPU License
>> LF : Application Specific Standby CPU License
>> LR : Application Specific Server License
>> LV : Application Specific Standby Server License
>> DH : Development and Testing Chip License
>> CH : Chip License
>> SH : Standby Chip License
>> AH : Application Deployment Chip License
>> BH : Application Deployment Standby Chip License
>> LH : Application Specific Chip License
>> LI : Application Specific Standby Chip License
>> Unknown
>> .
>>
>>
>>
>> Thanks in advance,
>>
>>
>>
>> --------------
>> Wilfredo Molina

# Mon Jan 31 10:32:11 CST 2011
# Replay feature output
# ---------------------
# This file was built by the Replay feature of InstallAnywhere.
# It contains variables that were set by Panels, Consoles or Custom Code.



#Validate Response File
#----------------------
RUN_SILENT=true

#Choose Install Folder
#---------------------
USER_INSTALL_DIR=C:\\sybase

#Choose Update Install Option
#----------------------------
DO_UPDATE_INSTALL=false

#Choose Install Set
#------------------
CHOSEN_FEATURE_LIST=fase_srv,fase_add_lm,fopen_client,fdblib,fjconnect60,fjconnect70,fodbcw,fado,fmcl,fdbisql,fqptune,fsc,fasep,fsysamp,famc,fsysam_util,fua,fase_agent,fase_snmp_agent
CHOSEN_INSTALL_FEATURE_LIST=fase_srv,fase_add_lm,fopen_client,fdblib,fjconnect60,fjconnect70,fodbcw,fado,fmcl,fdbisql,fqptune,fsc,fasep,fsysamp,famc,fsysam_util,fua,fase_agent,fase_snmp_agent
CHOSEN_INSTALL_SET=Custom

#Choose Product License Type
#---------------------------
SYBASE_PRODUCT_LICENSE_TYPE=license

#Choose Sybase Software Asset Management License
#-----------------------------------------------
SYSAM_LICENSE_SOURCE=license_file
SYSAM_LICENSE_FILE_PATHNAME=C:\\Users\\sybase\\Desktop\\RDS_200902200826.lic
SYSAM_EXISTING_LICENSE_SERVER_HOSTNAME=srvlnb11
SYSAM_EXISTING_LICENSE_SERVER_PORTNUMBER=

#Choose SYSAM Product Edtion and License Type
#--------------------------------------------
SYSAM_PRODUCT_EDITION=Small Business Edition
SYSAM_LICENSE_TYPE=SR : Server License

#Software Asset Management Notification Setting
#----------------------------------------------
SYSAM_NOTIFICATION_ENABLE=true
SYSAM_NOTIFICATION_SMTP_HOSTNAME=smtp.lnb.gob.sv
SYSAM_NOTIFICATION_SMTP_PORTNUMBER=465
SYSAM_NOTIFICATION_SENDER_EMAIL=dba@lnb.gob.sv
SYSAM_NOTIFICATION_RECIPIENT_EMAIL=wilfredo.molina@lnb.gob.sv
SYSAM_NOTIFICATION_EMAIL_SEVERITY=WARNING

#Remember ASE Password
#---------------------
ASEP_REMEMBER_PASSWORD=FALSE

#Configure New Servers
#---------------------
SY_CONFIG_ASE_SERVER=true
SY_CONFIG_BS_SERVER=true
SY_CONFIG_XP_SERVER=true
SY_CONFIG_JS_SERVER=true
SY_CONFIG_MS_SERVER=true
SY_CONFIG_SM_SERVER=true
SY_CONFIG_WS_SERVER=false
SY_CONFIG_UA_SERVER=true
SY_CONFIG_TXT_SERVER=false

#Configure New Adaptive Server
#-----------------------------
SY_CFG_ASE_SERVER_NAME=CENTRAL_DS
SY_CFG_ASE_PORT_NUMBER=5000
SY_CFG_ASE_APPL_TYPE=MIXED
SY_CFG_ASE_PAGESIZE=4k
SY_CFG_ASE_MASTER_DEV_NAME=E:\\data\\master_dd_1.dat
SY_CFG_ASE_MASTER_DEV_SIZE=128
SY_CFG_ASE_MASTER_DB_SIZE=100
SY_CFG_ASE_SYBPROC_DEV_NAME=E:\\data\\sysprocs_dd_1.dat
SY_CFG_ASE_SYBPROC_DEV_SIZE=256
SY_CFG_ASE_SYBPROC_DB_SIZE=200
SY_CFG_ASE_SYBTEMP_DEV_NAME=E:\\data\\sybsysdb_dd_1.dat
SY_CFG_ASE_SYBTEMP_DEV_SIZE=128
SY_CFG_ASE_SYBTEMP_DB_SIZE=64
SY_CFG_ASE_ERROR_LOG=C:\\sybase\\ASE-15_0\\install\\CENTRAL_DS.log
SY_CFG_ASE_PCI_ENABLE=false
SY_CFG_ASE_PCI_DEV_NAME=$NULL$
SY_CFG_ASE_PCI_DEV_SIZE=$NULL$
SY_CFG_ASE_PCI_DB_SIZE=$NULL$
SY_CFG_ASE_TEMP_DEV_NAME=F:\\data\\tempdb_dd_1.dat
SY_CFG_ASE_TEMP_DEV_SIZE=6144
SY_CFG_ASE_TEMP_DB_SIZE=6144
SY_CFG_ASE_OPT_ENABLE=false
SY_CFG_ASE_CPU_NUMBER=$NULL$
SY_CFG_ASE_MEMORY=$NULL$

#Configure New Backup Server
#---------------------------
SY_CFG_BS_SERVER_NAME=CENTRAL_DS_BS
SY_CFG_BS_PORT_NUMBER=5001
SY_CFG_BS_ERROR_LOG=C:\\sybase\\ASE-15_0\\install\\CENTRAL_DS_BS.log

#Configure New Monitor Server
#----------------------------
SY_CFG_MONITOR_SERVER_NAME=CENTRAL_DS_MS
SY_CFG_MONITOR_PORT_NUMBER=5002
SY_CFG_MONITOR_ERROR_LOG=C:\\sybase\\ASE-15_0\\install\\CENTRAL_DS_MS.log

#Configure New XP Server
#-----------------------
SY_CFG_XP_SERVER_NAME=CENTRAL_DS_XP
SY_CFG_XP_PORT_NUMBER=5003
SY_CFG_XP_ERROR_LOG=C:\\sybase\\ASE-15_0\\install\\CENTRAL_DS_XP.log

#Configure New Job Scheduler
#---------------------------
SY_CFG_JS_SERVER_NAME=CENTRAL_DS_JSAGENT
SY_CFG_JS_PORT_NUMBER=4900
SY_CFG_JS_MANAG_DEV_NAME=C:\\sybase\\data\\sybmgmt_dd_1.dat
SY_CFG_JS_MANAG_DEV_SIZE=256
SY_CFG_JS_MANAG_DB_SIZE=100

#Configure Self Management
#-------------------------
SY_CFG_SM_USER_NAME=sa
SY_CFG_SM_PASSWORD=

#Unified Agent - Self Discovery Service Adaptor
#----------------------------------------------
UAF_SELFDISCOVERY_CONFIG_UDP_ADAPTOR=true
UAF_SELFDISCOVERY_CONFIG_JINI_ADAPTOR=false
UAF_SELFDISCOVERY_JINI_HOST_NAME=localhost
UAF_SELFDISCOVERY_JINI_PORT_NUMBER=4160
UAF_SELFDISCOVERY_JINI_HEART_BEAT_PERIOD=900

#Unified Agent - Security Login Modules
#--------------------------------------
UAF_LOGIN_MODULES_SIMPLE_ACTIVE=true
UAF_LOGIN_MODULES_SIMPLE_USERNAME=uafadmin
UAF_LOGIN_MODULES_SIMPLE_PASSWORD=Sybase4me
UAF_LOGIN_MODULES_NTUNIX_ACTIVE=false
UAF_LOGIN_MODULES_ASE_ACTIVE=true
UAF_LOGIN_MODULES_MODULE_ORDER=SIMPLE1,ASE,NT


"Mark A. Parsons" <iron_horse Posted on 2011-01-31 18:33:32.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: ASE 15.5 intallation from a resource file
References: <4d434f7f$1@forums-1-dub> <4d45af9b$1@forums-1-dub> <4d46fa0d@forums-1-dub>
In-Reply-To: <4d46fa0d@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4d47007c$1@forums-1-dub>
Date: 31 Jan 2011 10:33:32 -0800
X-Trace: forums-1-dub 1296498812 10.22.241.152 (31 Jan 2011 10:33:32 -0800)
X-Original-Trace: 31 Jan 2011 10:33:32 -0800, vip152.sybase.com
Lines: 222
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:29909
Article PK: 79138

Glad to hear you got the details worked out and the silent install running!

As for your English skills ... they're not bad ... I've understand everything you've written. ;-)

On 01/31/2011 13:06, Wilfredo Molina wrote:
> I am so grateful for your help Mark!
>
> I think I got confused with the response and resource file.
>
> Before I write to the group I run the setupConsole program with no full
> path to a response file and I didn't find the response file anywhere as
> you said.
>
> But, as you write, with a full path I got the responsefile. Then I
> executed the setupConsole programa to install ASE 15.5 completely in
> silent mode without errors.
>
> There was a little detail. I'm installing Sybase ASE 15.5 in Windows
> Server 2008 with a windows account called sybase. I run the setupConsole
> program in silent mode at command line but the typical authorization
> window appeared because the sybase account isn't the SO Administrator.
> So, I run a command line window as Administrator then executed the
> setupConsole program in silent mode with the response file and the
> installation was succesful.
>
> Well, the problem that I wrote at first with the SYSAM_LICENSE_TYPE
> property, was an incorrect value.
>
> I've attached the response file I got from the setupConsole program in
> record mode.
>
>
>
>
>
> Thank you so much!
>
>
> Excuse me for my writing. English isn't my primary language :)
>
>
> El 30/01/2011 12:36 p.m., Mark A. Parsons escribió:
>> It's been a looooong time since I used a *response* file for installing
>> the Sybase ASE software so I didn't want to say anything until I created
>> a ASE 15.5 *response* file myself ... but first some basics ...
>>
>> ------------------
>>
>> Typically the first thing you need to do is install the Sybase ASE
>> software.
>>
>> You use the setup[console] program to do this.
>>
>> You can perform this step in silent mode if you provide a *response*
>> file. The caveat is that you must have a *response* file, and as you've
>> discovered Sybase does a lousy job of telling you what a *response* file
>> looks like (and I still haven't found a sample *response* file in the
>> ASE 15.5 installation directory).
>>
>> The only way (it seems) to determine the *response* file format is to do
>> an initial run of the setup[console] program in interactive mode and
>> have it create a *response* file for you. Again, Sybase does a lousy
>> job of documenting this (ie, no concrete examples in the Install
>> manual). I had to run the setupconsole program a couple times before I
>> figured out the format:
>>
>> setupconsole -r<full_path_to_response_file>
>>
>> eg: setupconsole -r N:\install\initial_response_file.txt
>>
>> NOTE: For my initial try I provided just a filename, assuming the file
>> would get created in the same directory where I kicked off the
>> setupconsole program. While the setupconsole program ran and
>> successfully installed the ASE software and configured an initial ASE
>> dataserver, it did not create a *response* file (if it did create the
>> file, I haven't been able to locate it on my machine). So, make sure
>> you provide a fully qualified path for the *response* file.
>>
>> The output file will be in ascii text format. (For windows environments
>> you may need to open with WordPad to get the CR/LFs properly read.)
>>
>> I've attached my *response* file [initial_response_file.txt].
>>
>> ------------------
>>
>> Once the ASE software's been installed you can then look at creating
>> your dataserver(s).
>>
>> The setup[console] program gives you the option to setup an initial
>> dataserver immediately after the ASE software has been installed. If
>> you run setup[console] in record mode (ie, create a *response* file),
>> you'll see the dataserver creation details in the later part of the
>> *response* file (see my attached *response* file).
>>
>> If you prefer to create a dataserver separate from the installation of
>> the ASE software, then you can either go the manual route and use the
>> dataserver program (not recommended for newbies), or you can use the
>> srvbuild[res]/asecfg/sybatch/syconfig tools (depends on your OS). If
>> you want to create a dataserver in silent mode then you need to have a
>> *resource* file, which is turn is fed to the srvbuildres/sybatch programs.
>>
>> ------------------
>>
>> OK, now that we've got the basics out of the way ... and newbies are no
>> doubt a tad bit confused ... we can look at your post ...
>>
>> The first item we need to address is terminology (per Sybase's definition).
>>
>> A *response* file is used to install the ASE software (and if desired
>> create an initial ASE dataserver). The *response* file is created/used
>> by the setup[console] programs.
>>
>> A *resource* file is used, *after* the ASE software has been installed,
>> to create a ASE dataserver. The *resource* file is used by the
>> srvbuildres/sybatch programs.
>>
>> Next item is the format of these two files.
>>
>> The *response* and *resource* files have different formats.
>>
>> The file you attached to your post is formatted as a *resource* file,
>> and has nothing to do with the installation of ASE software. (I'm not
>> sure why you added the 7 UNIX-like variable settings at the beginning of
>> the file ... ??? I can't say with 100% certainty that those variables
>> are ignored ... but I don't recall ever seeing that kind of format in a
>> *resource* file ... ?)
>>
>> Sybase does provide some sample *resource* files which you can normally
>> find with a '.res' extension (buried somewhere in your ASE software
>> directory). ['.res' in Windows; not sure at the moment what the
>> linux/unix extension looks like]
>>
>> Again, Sybase doesn't seem to provide any *response* file samples so
>> you're left having to perform an initial run of the setup[console]
>> program in record mode (-r).
>>
>> ------------------
>>
>> Regarding those 7 UNIX-like variables settings ...
>>
>> Those do look like entries from a *response* file. (see my attachment)
>>
>> When I ran setupconsole I chose to install the developer version; my
>> guess is that if you run setup[console] in record mode (-r) that you'll
>> find those UNIX-like variable settings (for Small Business/SR) show up
>> in the *response* file created by setup[console]. ("Duh, Mark!" ?)
>>
>>
>>
>>
>>
>>
>> On 01/28/2011 18:21, Wilfredo Molina wrote:
>>> Hello,
>>>
>>>
>>> I am attempting to install ASE 15.5 in silent mode from a resource file
>>> but I am having some errors.
>>>
>>> I attach the resource file sqlsrv.res
>>>
>>> I executed the next line at command line and get the error "ERROR:The
>>> property SYSAM_LICENSE_TYPE value is not specified or not valid." In the
>>> next lines I get what are the optional values the SYSAM_LICENSE_TYPE
>>> property should have. I added the SYSAM property to the resource file
>>> but I still get the error. What can I do?
>>> I didn't find too much documentation about creating resource files for
>>> ASE 15.
>>>
>>> _________________________________________________________________
>>> C:\sybase>d:\ase1550_winx64_v2\setupConsole.exe -f C:\sybase\sqlsrv.res
>>> -i silent
>>> Preparing SILENT Mode Installation...
>>>
>>> ===============================================================================
>>>
>>> Sybase Adaptive Server Enterprise Suite (created with
>>> InstallAnywhere)
>>> -------------------------------------------------------------------------------
>>>
>>>
>>> ERROR:The property SYSAM_LICENSE_TYPE value is not specified or not
>>> valid.
>>> The optional values for property SYSAM_LICENSE_TYPE:
>>> CP : CPU License
>>> SF : Standby CPU License
>>> SR : Server License
>>> SV : Standby Server License
>>> DT : Development and Test License
>>> EV : Evaluation License
>>> OT : Other License
>>> SS : Standalone Seat License
>>> DV : Developer License
>>> NA : Not Applicable or Other License
>>> AC : OEM Application Deployment CPU License
>>> BC : OEM Application Deployment Standby CPU License
>>> AR : OEM Application Deployment Server License
>>> BR : OEM Application Deployment Standby Server License
>>> AO : OEM Application Deployment Other License
>>> LP : Application Specific CPU License
>>> LF : Application Specific Standby CPU License
>>> LR : Application Specific Server License
>>> LV : Application Specific Standby Server License
>>> DH : Development and Testing Chip License
>>> CH : Chip License
>>> SH : Standby Chip License
>>> AH : Application Deployment Chip License
>>> BH : Application Deployment Standby Chip License
>>> LH : Application Specific Chip License
>>> LI : Application Specific Standby Chip License
>>> Unknown
>>> .
>>>
>>>
>>>
>>> Thanks in advance,
>>>
>>>
>>>
>>> --------------
>>> Wilfredo Molina
>