Sponsored Content
Top Forums Shell Programming and Scripting UNIX script to validate the export of a XML-formatted mapping Post 302786649 by sampoorna on Thursday 28th of March 2013 12:41:27 AM
Old 03-28-2013
Yes, the mapping should be a valid one and the naming conventions should should be as per the standard codes. That is basically the script should check the XML file and validate the naming conventions of all the objects in the mapping.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

unix script to export data from csv file to oracle database

Hello people, Need favour. The problem I have is that, I need to develop a unix shell script that performs recurring exports of data from a csv file to an oracle database. Basically, the csv file contains just the first name and last name will be dumped to an Unix server. The data from these... (3 Replies)
Discussion started by: vinayagan
3 Replies

2. UNIX for Dummies Questions & Answers

Export xml to windows machine

Hi, i am a real dummy about unix. i need your suggestions about an issue. my problem is that i have a oracle db on unix machine. i will create a procedure on that database which will produce an xml file. however, i need to place this xml to a windows machine and want to make it with pl/sql... (1 Reply)
Discussion started by: merope
1 Replies

3. UNIX for Dummies Questions & Answers

Call unix script through informatica mapping

hi, i want to call unix script from transformations used in informatica mapping? can we do it in any way? Please reply ASAP. We cant use Storep procedure transformation Thanks in Advance nishith (0 Replies)
Discussion started by: Nishithinfy
0 Replies

4. UNIX for Advanced & Expert Users

Can any one share a unix script for validating the export of a mapping which is in XM

Hi, Can any one share a unix script for validating the export of a mapping which is in XML format. like my requirment is that when ever we are migrating the mappings or wokflows from development to QA we will take the export of that mapping into an XML file.Insted of reviewing the mapping... (1 Reply)
Discussion started by: perlamohan
1 Replies

5. Shell Programming and Scripting

Can any one share a unix script for validating the export of a mapping which is in XM

Hi, Can any one share a unix script for validating the export of a mapping which is in XML format. like my requirment is that when ever we are migrating the mappings or wokflows from development to QA we will take the export of that mapping into an XML file.Insted of reviewing the mapping... (1 Reply)
Discussion started by: perlamohan
1 Replies

6. Shell Programming and Scripting

Mapping name into unix script

Hi, How do i call a mapping name and workflow name of an informatica tool in the unix script inorder to execute the mapping. It would be great if any one of u help me in getting a mapping name in a unix script. Thanks in advance (0 Replies)
Discussion started by: raji35
0 Replies

7. Shell Programming and Scripting

I need script to get xml access export from source server

Hi, I need a shell script to create to get XML access export from the source server. Thanks in Advance (3 Replies)
Discussion started by: bcb
3 Replies

8. Shell Programming and Scripting

XMLLINT COMMAND IN UNIX TO VALIDATE XML AGAINST XSD

Hi i am baby to unix shell script. how do i validate xml agaist xsd and transforms xml using xslt. Thanks Mohan (2 Replies)
Discussion started by: mohan.cheepu
2 Replies

9. Shell Programming and Scripting

Validate xml agaist xsd is ksh

how do i validate xml agaist xsd is ksh? (1 Reply)
Discussion started by: LiorAmitai
1 Replies

10. Shell Programming and Scripting

Data export UNIX shell script

Hi, I want to write a shell script which connect to my database with the following credentials : User name : user PWD : rap_user_1 Hostname : app.Unix.Gsm1900.Org Port : 7862 SID : PTNC1 Once connected to DB i want to fetch data with the help of a SQL statement and expoet... (4 Replies)
Discussion started by: neeraj617
4 Replies
lpc(1B) 					     SunOS/BSD Compatibility Package Commands						   lpc(1B)

NAME
lpc - line printer control program SYNOPSIS
/usr/ucb/lpc [ command [ parameter...]] DESCRIPTION
The lpc utility controls the operation of local printers. Use lpc to perform the following functions: o start or stop a printer, o disable or enable a printer's spooling queue, o rearrange the order of jobs in a print queue, or o display the status of a printer print queue and printer daemon. lpc can be run from the command line or interactively. Specifying lpc with the optional command and parameter arguments causes lpc to interpret the first argument as an lpc command, and all other arguments as parameters to that command. Specifying lpc without arguments causes it to run interactively, prompting the user for lpc commands with lpc>. By redirecting the standard input, lpc can read commands from a file. USAGE
lpc commands may be typed in their entirety or abbreviated to an unambiguous substring. Some lpc commands are available to all users; oth- ers are available only to super-users. All users may execute the following lpc commands: ? [command ...] | help [command ...] Displays a short description of command. command is an lpc command. If command is not specified, displays a list of lpc commands. exit | quit Exits from lpc. status [all | printer ...] Displays the status of print daemons and print queues. all specifies that this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for infor- mation regarding naming conventions for atomic names. Only a super-user may execute the following lpc commands: abort [all | printer ...] Terminates an active spooling daemon. Disables printing (by preventing new daemons from being started by lpr(1B)) for printer. all specifies this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. clean [all | printer ...] Removes files created in the print spool directory by the print daemon from printer 's print queue. all specifies that this command is performed on all locally attached printers.printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. disable [all | printer ...] Turns off the print queue for printer. Prevents new printer jobs from being entered into the print queue for printerby lpr(1B). all specifies that this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. down [all | printer ...] [message] Turns the queue for printer off and disables printing on printer. Inserts message in the printer status file. message does not need to be quoted; multiple arguments to message are treated as arguments are to echo(1). Use down to take a printer down and inform users. all specifies that this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. enable [all | printer ...] Enables lpr(1B) to add new jobs in the spool queue. all specifies that this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for infor- mation regarding naming conventions for atomic names. restart [all | printer ...] Attempts to start a new printer daemon. restart is useful when a print daemon dies unexpectedly and leaves jobs in the print queue. all specifies that this command is performed on all locally attached printers. printer indicates that this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. start [all | printer ...] Enables printing. Starts a spooling daemon for the printer. all specifies that this command is performed on all locally attached printers. printer indicates the command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. stop [all | printer ...] Stops a spooling daemon after the current job is complete. Disables printing at that time. all specifies that this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. topq printer [request-ID ...] [user ...] Moves request-ID or print jobs belonging to user on printer to the beginning of the print queue. Specify user as a user's login name. Specify printer as an atomic name. See printers.conf(4) for information regarding naming conventions for atomic names. up [all | printer ...] Turns the queue for printer on and enables printing on printer. Deletes the message in the printer status file (inserted by down). Use up to undo the effects of down. all specifies that this command is performed on all locally attached printers. printer indicates this command is performed on specific printers. Specify printer as an atomic name. See printers.conf( 4) for information regarding naming conventions for atomic names. EXIT STATUS
The following exit values are returned: 0 Successful completion. non-zero An error occurred. FILES
/var/spool/lp/* LP print queue. /var/spool/lp/system/pstatus Printer status information file. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWscplp | +-----------------------------+-----------------------------+ SEE ALSO
echo(1), lpq(1B), lpr(1B), lprm(1B), lpstat(1), lpsched(1M), lpshut(1M), svcadm(1M), printers.conf(4), attributes(5) DIAGNOSTICS
Use the svcs(1) utility to check if svc:/application/print/server is running. If it is not running, use svcadm enable svc:/applica- tion/print/server to start lpsched. See svcadm(1M). Ambiguous command Indicates that the lpc command or abbreviation matches more than one command. ?Invalid command Indicates that the lpc command or abbreviation is not recognized. ?Privileged command Indicates that the lpc command or abbreviation can be executed only by a super-user. lpc: printer: unknown printer to the print service Indicates that printer does not exist in the LP database. Check that printer was correctly specified. Use lpstat -p or the status command (see lpstat(1) or USAGE) to check the status of printers. lpc: error on opening queue to spooler Indicates that the connection to lpsched failed. Usually means that the printer server has died or is hung. Use /usr/lib/lp/lpsched to check if the printer spooler daemon is running. lpc: Can't send message to LP print service lpc: Can't receive message from LP print service Indicates that the LP print service stopped. Contact the LP administrator. lpc: Received unexpected message from LP print service Indicates a problem with the software. Contact the LP administrator. SunOS 5.10 5 Aug 2004 lpc(1B)
All times are GMT -4. The time now is 01:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy