Sponsored Content
Top Forums Shell Programming and Scripting how to call to unix through cobol Post 302093366 by naamas03 on Thursday 19th of October 2006 04:36:51 AM
Old 10-19-2006
hi
the result are :
UX:ls: ERROR: Cannot access /home/hoz_shl/where/script/resides/cs-tr-700
No such file or directory UX:ls: ERROR: Cannot access 00000000: No such file or directory UX:sh (sh)
UX:sh (sh): ERROR: sh: syntax error at line 3: `(' unexpec
the script doing like that
cs-tr-700
#!/bin/sh
mv cost_04200a cost_04200a_m
tr -d "\015" <cost_04200a_m> cost_04200a
please help
 

10 More Discussions You Might Find Interesting

1. Solaris

Cobol linking in Unix

I'm trying to call a C mod from COBOL but I'm currently having difficulty linking my COBOL program with a C module that I've just developed. I've tried using cbllink -v -l -k -BSF CMPCACVN.cbl test.lib but I've got an error that states cbllink: not found. I've also tried using buildclient -C -w -o... (0 Replies)
Discussion started by: soulfactory2002
0 Replies

2. UNIX for Dummies Questions & Answers

Cobol On Unix

Hi , Could anyone please tell me about the whole procedure for compiling, linking the cobol program on unix platform. As i am mainframe guy and very new to unix, any help will be very appriciated, Regards, -Vinit (2 Replies)
Discussion started by: vinit_cyberguy
2 Replies

3. UNIX for Dummies Questions & Answers

Newbie's question about COBOL Installation in Unix

I wanna to install a COBOL on the AIX unix server. Would u like to tell me the disk usage of COBOL installation? Thanks in advance. (2 Replies)
Discussion started by: GCTEII
2 Replies

4. Programming

cobol crn programme run on express cobol as .gnt

can i run .crn programme in express cobol which support to .gnt programme .... Plz tell me solution (2 Replies)
Discussion started by: bibi
2 Replies

5. Shell Programming and Scripting

Calling script from RM cobol and returning value to cobol

Is there a way you can return a value from a script that is called from a rm cobol program... 01 WS-COMD-LINE-PGM X(39) value sh ./getUserId.sh 12345" 01 WS-RETURN-SYS-CODE PIC 9(8). CALL "SYSTEM" USING WS-COMD-LINE-PGM GIVING WS-RETURN-SYS-CODE. ... (1 Reply)
Discussion started by: pavanmp
1 Replies

6. Programming

Acceessing DB2 UDB in AIX COBOL on unix

Hi , We are migrating our database from DB2 z/os to DB2 UDB on UNIX. and cobol on mainframes to AIX cobol on UNIX. We have some cobol Db2 programs that are accessing different Databases how do we code such type of programs in AIX cobol. Do we need to Establish connection for accessing... (0 Replies)
Discussion started by: nal.satish
0 Replies

7. UNIX for Dummies Questions & Answers

UNIX Scripts "Load Error" with MicroFocus COBOL subprograms

When running our UNIX job scripts we randomly get the following 198 error below. When we restart the job it works fine. I haven't been able to recreate the problem in test, so I'm wondering if it has something to do with Cron or possibly a memory error or memory leak. I don't see anything... (5 Replies)
Discussion started by: rthiele
5 Replies

8. Programming

UNIX system call in COBOL

Hi, The UNIX system call inside the COBOL program is doing the specified command correctly. MOVE W080-UNZIP-FILE-COMMAND TO W080-OUTPUT-COMMAND CALL "SYSTEM" USING W080-OUTPUT-COMMAND RETURNING W080-SYS-CALL-STATUS BUT The problem is, the following keeps on showing on the log file... (2 Replies)
Discussion started by: joyAV
2 Replies

9. Programming

UNIX commad in COBOL

Hi guys, i used the call "sytem" using ... in a cobol program. At the moment i stoped at an empasse, how cam I retrive the execution's result of unix command? Explenation, I made an 'pwd' command, and I must to have the directory inside the program. How can have this result? (2 Replies)
Discussion started by: Prosy60
2 Replies

10. UNIX and Linux Applications

Ms COBOL 2.2 for SCO UNIX

HI ALL, I'm searching Ms Cobol 2.2 for Sco Unix if anyone has it please kind enough to support me... Thanks in advance Rukshan:) (2 Replies)
Discussion started by: rukshan4u2c
2 Replies
CREATE 
DATABASE(7) SQL Commands CREATE DATABASE(7) NAME
CREATE DATABASE - create a new database SYNOPSIS
CREATE DATABASE name [ [ WITH ] [ OWNER [=] dbowner ] [ LOCATION [=] 'dbpath' ] [ TEMPLATE [=] template ] [ ENCODING [=] encoding ] ] INPUTS name The name of a database to create. dbowner Name of the database user who will own the new database, or DEFAULT to use the default (namely, the user executing the command). dbpath An alternate file-system location in which to store the new database, specified as a string literal; or DEFAULT to use the default location. template Name of template from which to create the new database, or DEFAULT to use the default template (template1). encoding Multibyte encoding method to use in the new database. Specify a string literal name (e.g., 'SQL_ASCII'), or an integer encoding num- ber, or DEFAULT to use the default encoding. OUTPUTS CREATE DATABASE Message returned if the command completes successfully. ERROR: user 'username' is not allowed to create/drop databases You must have the special CREATEDB privilege to create databases. See CREATE USER [create_user(7)]. ERROR: createdb: database "name" already exists This occurs if a database with the name specified already exists. ERROR: database path may not contain single quotes The database location dbpath cannot contain single quotes. This is required so that the shell commands that create the database directory can execute safely. ERROR: CREATE DATABASE: may not be called in a transaction block If you have an explicit transaction block in progress you cannot call CREATE DATABASE. You must finish the transaction first. ERROR: Unable to create database directory 'path'. ERROR: Could not initialize database directory. These are most likely related to insufficient permissions on the data directory, a full disk, or other file system problems. The user under which the database server is running must have access to the location. DESCRIPTION
CREATE DATABASE creates a new PostgreSQL database. Normally, the creator becomes the owner of the new database. Superusers can create databases owned by other users using the OWNER clause. They can even create databases owned by users with no special privileges. Non-superusers with CREATEDB privilege can only create databases owned by themselves. An alternate location can be specified in order to, for example, store the database on a different disk. The path must have been prepared with the initlocation [initlocation(1)] command. If the path name does not contain a slash, it is interpreted as an environment variable name, which must be known to the server process. This way the database administrator can exercise control over locations in which databases can be created. (A customary choice is, e.g., PGDATA2.) If the server is compiled with ALLOW_ABSOLUTE_DBPATHS (not so by default), absolute path names, as identified by a leading slash (e.g., /usr/local/pgsql/data), are allowed as well. By default, the new database will be created by cloning the standard system database template1. A different template can be specified by writing TEMPLATE = name. In particular, by writing TEMPLATE = template0, you can create a virgin database containing only the standard objects predefined by your version of PostgreSQL. This is useful if you wish to avoid copying any installation-local objects that may have been added to template1. The optional encoding parameter allows selection of the database encoding, if your server was compiled with multibyte encoding support. When not specified, it defaults to the encoding used by the selected template database. Optional parameters can be written in any order, not only the order illustrated above. NOTES CREATE DATABASE is a PostgreSQL language extension. Use DROP DATABASE [drop_database(7)] to remove a database. The program createdb [createdb(1)] is a shell script wrapper around this command, provided for convenience. There are security and data integrity issues involved with using alternate database locations specified with absolute path names, and by default only an environment variable known to the backend may be specified for an alternate location. See the Administrator's Guide for more information. Although it is possible to copy a database other than template1 by specifying its name as the template, this is not (yet) intended as a general-purpose COPY DATABASE facility. We recommend that databases used as templates be treated as read-only. See the Administrator's Guide for more information. USAGE
To create a new database: olly=> create database lusiadas; To create a new database in an alternate area ~/private_db: $ mkdir private_db $ initlocation ~/private_db The location will be initialized with username "olly". This user will own all the files and must also own the server process. Creating directory /home/olly/private_db Creating directory /home/olly/private_db/base initlocation is complete. $ psql olly Welcome to psql, the PostgreSQL interactive terminal. Type: copyright for distribution terms h for help with SQL commands ? for help on internal slash commands g or terminate with semicolon to execute query q to quit olly=> CREATE DATABASE elsewhere WITH LOCATION = '/home/olly/private_db'; CREATE DATABASE COMPATIBILITY
SQL92 There is no CREATE DATABASE statement in SQL92. Databases are equivalent to catalogs, whose creation is implementation-defined. SQL - Language Statements 2002-11-22 CREATE DATABASE(7)
All times are GMT -4. The time now is 03:54 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy