Phase Dependency in DAC

Hi,
We are upgrading our applications from 7.8.3 to OBI 7.9.4, with keeping our 7.8.3 data model (SRMW) as is.
In DAC 7.8.3 under task definition we have 'depends on task' and 'dependent task’ whereas in 7.9.4 we have phase dependency. in 7.8.3, we could actually give the dependent tasks name (Commands) and in 7.9.4 we have to give the phases dependency for that task (such as extract dimension, load fact etc...)
How should we go ahead in developing tasks, if we want to retain the 7.8.3 DAC functionality?
Thank You,
Kapil

Hi Kapil,
There is way to set the dependency. Check if you can create the task gruops and define the execution order there.
Please read more about the Crating Task Groups in DAC guide.
Regards,
Ashish

Similar Messages

Update Row into Run Table Task is not executing in correct sequence in DAC

Update Row into Run Table Task is not executing in correct sequence in DAC.
The task phase for this task is "Post Lost" . The depth in the execution plan is 19 but this task is running some times in Depth 12, some times in 14 and some time in Depth 16. Would like to know is this sequence of execution is correct order or not? In the out of the Box this task is executed at the end of the entire load. No Errors were reported in DAC log.
Please let me know if any documents that would highlight this issue
rm

Update into Run table is a task thats required to update a table called W_ETL_RUN_S. The whole intention of this table is to keep the poor mans run history on the warehouse itself. The actual run history is stored in the DAC runtime tables, however the DAC repository could be on some other database/schema other than warehouse. Its mostly a legacy table, thats being carried around. If one were to pay close attention to this task, it has phase dependencies defined that dictate when this task should run.
Apologies in advance for a lengthy post.... But sure might help understanding how DAC behaves! And is going to be essential for you to find issues at hand.
The dependency generation in DAC follows the following rules of thumb!
- Considers the Source table target table definitions of the tasks. With this information the tasks that write to a table take precedence over the tasks that reads from a table.
- Considers the phase information. With this information, it will be able to resolve some of the conflicts. Should multiple tasks write to the same table, the phase is used to appropriately stagger them.
- Considers the truncate table option. Should there be multiple tasks that write to the same table with the same phase information, the task that truncates the table takes precedence.
- When more than one task that needs to write to the table that have similar properties, DAC would stagger them. However if one feels that either they can all go in parallel, or a common truncate is desired prior to any of the tasks execution, one could use a task group.
- Task group is also handy when you suspect the application logic dictates cyclical reads and writes. For example, Task 1 reads from A and writes to B. Task 2 reads from B and writes back to A. If these two tasks were to have different phases, DAC would be able to figure that out and order them accordingly. If not, for example those tasks need to be of the same phase for some reason, one could create a task group as well.
Now that I described the behavior of how the dependency generation works, there may be some tasks that have no relevance to other tasks either as source tables or target tables. The update into run history is a classic example. The purpose of this task is to update the run information in the W_ETL_RUN_S with status 'Completed' with an end time stamp. Because this needs to run at the end, it has phase dependency defined on it. With this information DAC will be able to stagger the position of execution either before (Block) or after (Wait) all the tasks belonging to a particular phase is completed.
Now a description about depth. While Depth gives an indication to the order of execution, its only an indication of how the tasks may be executed. Its a reflection of how the dependencies have been discovered. Let me explain with an example. The tasks that have no dependency will have a depth of 0. The tasks that depend on one or more or all of depth 0 get a depth of 1. The tasks that depend on one or more or all of depth 1 get a depth of 2. It also means implicitly a task of depth 2 will indirectly depend on a task of depth 0 through other tasks in depth 1. In essence the dependencies translate to an execution graph, and is different from the batch structures one usually thinks of when it comes to ETL execution.
Because DAC does runtime optimization in the order in which tasks are executed, it may pick a task thats of order 1 over something else with an order of 0. The factors considered for picking the next best task to run depend on
- The number of dependent tasks. For example, a task which has 10 dependents gets more priorty than the one whose dependents is 1.
- If all else equal, it considers the number of source tables. For example a task having 10 source tables gets more priority than the one that has only two source tables.
- If all else equal, it considers the average time taken by each of the tasks. The longer running ones will get more preference than the quick running ones
- and many other factors!
And of course the dependencies are honored through the execution. Unless all the predecessors of a task are in completed state a task does not get picked for execution.
Another way to think of this depth concept : If one were to execute one task at a time, probably this is the order in which the tasks will be executed.
The depth can change depending on the number of tasks identified for the execution plan.
The immediate predecessors and successor can be a very valuable information to look at and should be used to validate the design. All predecessors and successors provide information to corroborate it even further. This can be accessed through clicking on any task and choosing the detail button. You will see all these information over there. As an alternate method, you could also use the 'All/immediate Predecessors' and 'All/immediate Successor' tabs that provide a flat view of the dependencies. Note that these tabs may have to retrieve a large amount of data, and hence will open in a query mode.
SUMMARY: Irrespective of the depth, validate
- if this task has 'Phase dependencies' that span all the ETL phases and has a 'Wait' option.
- click on the particular task and verify if the task does not have any successors. And the predecessors include all the tasks from all the phases its supposed to wait for!
Once you have inspected the above two you should be good to go, no matter what the depth says!
Hope this helps!

DAC ORDERED TASK

Hi,
The DAC orders the tasks automaticly according to task's parent group and task's dependencies.
My question is : can i order the task manually or in another word to determine the depth of the task manually?
Thanks

Hi
DAC ordrers the tasks automatically using the source and target information which it gets after task synchronization.
If you want to keep your own dependency either you can add the target table of the preceeding task after which
you want to run this particular task.....or set the phase dependency....accordingly....
Regards

Installation ABAP import phase problem

Dear Friends,
I am installing ABAP application server within Netweaver 7.02 which has been downloaded from this site on my LAPTOP.
Phases 1 -15 took about 2 hrs to install.
After that it entered Phase 16 i.e Import ABAP and it has gone on for more that 12 hrs.
Of the 37 processes in this phase the last 2 doesn't complete. One is shown as running and other is waiting.
My Laptop has around 320GB HDD(100 GB free) 4 GB RAM of which only 3GB is usable as it as 32 bit OS,2.4 GHZ Core 2 Duo
processor and Windows Vista.
I think it is abnormal to continue for so long.
It does not show any error message nor any problem in the log.
What is the problem?
Pls advise.
Thamk for your efforts.

Hi Sunny,
"Speed of this phase depends on number of things:
1) How many number of parallel jobs you have selected in sapinst ?
2) 4 GB of RAM is not much. So, it will take time."
1)How do I check the number of parallel jobs?
I think only one job is running because in the taskbar for the Installer it shows:
Import job Monitor: Running 1, Waiting 1, Failed 0, Completed 35, Total 37
The phase is Import ABAP and it has several jobs i.e threads of which only one is running.
2) Of the 4 Gb RAM only 3 GB is usable by Windows as it is 32 bit.Now of this Memory utilization is 65- 70%.
CPU utilization is 10-15%.
Since resource utilization is very less it is taking enormous amount of time.
As per documentation installation on a Laptop should not take more than 8 hrs but it has taken double the time i.e 16 hrs.
How much more time will it take?
Is there any way to speed it up ?
Thanks.

Phase difference measurement

I need assistance measuring the phase difference between two digital signals (0 to 5 volts). The signals are angle outputs of a rotating torque sensor. All of this is for the purpose of tracking the angle of rotation as I measure torque. Normally, I would run first angle to a counter and the second angle through an up/down gate on the DAQ board, however my board has no such up/down gate. The two signals are supposed to be 90 degrees out of phase depending on the direction of rotation. As such, Labview should then differentiate when to count up or count down the degrees of rotation. If I had a way of mathematically determining the phase of the signals, I could write a Labview vi to change the counting from one way to the other. I have already spent hours researching phase difference methods on the forums, however I am using Labview 8 base package, and therefore do not have access to advanced functions such as Hilbert Transforms or AC/DC Estimators. Any ideas? There has to be a way to use trig identities or something and solve out phase difference.
Matthew

Search for "quadrature encoder" on ni.com. Here is an extract from this link.
Quadrature Encoders
The most common type of incremental encoder uses two output channels (A and B) to sense position. Using two code tracks with sectors positioned 90° out of phase, the two output channels of the quadrature encoder indicate both position and direction of rotation. If A leads B, for example, the disk is rotating in a clockwise direction. If B leads A, then the disk is rotating in a counter-clockwise direction. Therefore, by monitoring both the number of pulses and the relative phase of signals A and B, you can track both the position and direction of rotation.
In addition, some quadrature detectors include a third output channel, called a zero or reference signal, which supplies a single pulse per revolution. This single pulse can be used for precise determination of a reference position.

Statuses and phases in the Opportunity

Hi,
Can any one tell me if there is a standard way of achieving the following config/business requirement in CRM 5.0.
Link/ Relate Statuses and Phases in the Opportunity.
Status in the Status Profile.
Active, Inprocess, Pending, Complete.
Phases in the Sales cycle.
Inprocess, Pending, Active, Complete.
Each Phase has some actions assignesd to it.
Now the requirement is to get the Phase determined by the Status and corresponding actions triggered in the Phases.
Many thanks,
Srinivasu

HI,
I believe you have a requirement where you need to set Phases depending on Status.
So, using the above mentioned badi, whenever a status is set, you can change the phase of the opportunity.
In case you wanna change status depending on Phases, you can use the follwoing badi: RM_OPPORT_H_BADI
Method: CRM_OPPORT_H_MERGE
and then use FM CRM_ORDER_CHANGE_STATUS_PUT_OW
to set the status
Hope this helps..
Kindly reward with points in case helpful
Sharif.

Exchange 2013 - Unbound Stretched Active/Active DAG

I'm designing an Active/Active DAG utilizing a 3-site scenario, with the third site for FSW.
I intend to have 3 CAS+MBX servers in each location.
Site A & B are separately co-located and Site C is geographically distant site for the FSW
Should the WAN connections of Site A go down (for whatever reason), do the passive copies of Site A's DB's on Site B automatically mount?
What happens with the copies in Site A when this is going on, and what occurs when the links are restored? Is there any manual intervention required here and is DAC/Split-Brain syndrome a concern at all?
What if the client doesn't want Auto-failover, can blockautoactivation be set for the passive DB's to -SiteOnly?

Hi Hayley,
Q:- Should the WAN connections of Site A go down (for whatever reason), do the passive
copies of Site A's DB's on Site B automatically mount?
Yes it could be automatically mount depends on DAC mode, you should enable it by default it is disable.
Q:- What happens with the copies in Site A when this is going on, and what occurs when the links
are restored? Is there any manual intervention required here and is DAC/Split-Brain syndrome a concern at all?
Site A copy would be like Passive Copy which will get the log shipping from Site B once the WAN link will be up and running, as the DAC mode is enable will not allow
the Site A database to mount its database once it will up and running,
You can later change your active copy to Site A.
Q: - What
if the client doesn't want Auto-failover, can blockautoactivation be set for the passive DB's to -SiteOnly?
Please check the below link for better understanding.
http://technet.microsoft.com/en-us/library/dd979790(v=exchg.150).aspx
Thanks & Regards
Ashish Gaur
Ashish Gaur

Appropriation Request , Approval

Hi All,
required help in mapping 1 senario.
1. AR passes from the approval phases depending upon the value and the data entered..
2. When the AR is approved the Approval will differ from the planed value , how to map this senario
with the Approval amount.
Regards
Hemant

Hi Hemant,
You'll need to take help from workflow consultant for this. This cannot be done in Standard.
WF can read plan values of the AR from relevant tables and choose the approval path accordingly.
pass IMAK-POSNR in IMAV. Read IMAV-OBJNR and pass its value in BPGE or BPJA to get the plan value for the AR.
Without overhead cost is value type 40, and with oH cost is 39
with regards,
Ravi Shrivastav

How to handle multiple part appraisers in OSA

how do I configure the system for two part-appraisers and one final appraiser?
1. do I need to configure two standard columns PAPP?
2. how do I autorize partappr1 to access PAPP column 1 and partappr2 to access PAPP column2?
3. how to specify who the part appraisers are? ex. john doe is partappr1 and mary jones is partappr2.
4. do I need two process steps in the process flow (step1="partappr1 feedback completed", step2="partappr2 feedback completed" )
Thanks,
Tiberiu

Hi Tiberiu,
1. do I need to configure two standard columns PAPP?
- No, one column is enough. system will occupy separate columns for each of the part appraisers.
2. how do I autorize partappr1 to access PAPP column 1 and partappr2 to access PAPP column2?
- In column access tab you can select "Phase dependent access for owner" ,in the Default field
3. how to specify who the part appraisers are? ex. john doe is partappr1 and mary jones is partappr2.
- There part appraiser names are determined when the form is first created by the HR specialist or the appraiser.
4. do I need two process steps in the process flow (step1="partappr1 feedback completed", step2="partappr2 feedback completed" )
- When you select part appraiser column, in status flow In Process - Part Appraiser in process substatus is automatically selected. You don't need a separate status. Please make sure that you hit "Set status" field while maintaining Part Appraiser in process substatus and determine the target status/substatus -probably In Process (by final appraiser)- when the last part appraiser is finished with the document.
Regards,
Dilek

SCCM 2012 R2, KB2910552 after Cumulative update 2

Hi !
I wask noticed for very slow package download at operating system deployment pahse in SCCM 2012R2 CU2. After little digging, I found possible sollution from http://support2.microsoft.com/kb/2910552, but installation failed, since system is updated CU2 after
R2 upgrade.
How should I proceed?
WIM File, application download etc seems fine at 100 or 1000 mbps wire, but any (driver, program) package takes from minutes to hours. No SSL, or antivirus is messing. Drivers and bios updated.
~T

I have noticed only traditional packages (including drivers) kills speed.
Installed R2CU3, updated Boot images, no change.
From running log
.....<![LOG[Set a global environment variable _SMSTSNextInstructionPointer=6]LOG]!><time="17:06:49.617-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:668">
<![LOG[Set a TS execution environment variable _SMSTSNextInstructionPointer=6]LOG]!><time="17:06:49.633-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:386">
<![LOG[Set a global environment variable _SMSTSInstructionStackString=0 5]LOG]!><time="17:06:49.633-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:668">
<![LOG[Set a TS execution environment variable _SMSTSInstructionStackString=0 5]LOG]!><time="17:06:49.633-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:414">
<![LOG[Save the current environment block]LOG]!><time="17:06:49.633-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:833">
<![LOG[Start executing an instruction. Instruction name: Dell. Instruction pointer: 6]LOG]!><time="17:06:49.883-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="engine.cxx:116">
<![LOG[Set a global environment variable _SMSTSCurrentActionName=Dell]LOG]!><time="17:06:49.883-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:668">
<![LOG[Set a global environment variable _SMSTSNextInstructionPointer=6]LOG]!><time="17:06:49.883-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:668">
<![LOG[Evaluating an AND expression]LOG]!><time="17:06:49.898-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="tsexpreval.cpp:600">
<![LOG[Evaluating a WMI condition expression]LOG]!><time="17:06:49.898-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="tsexpreval.cpp:1879">
<![LOG[Expand a string: root\cimv2]LOG]!><time="17:06:49.898-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="utility.cpp:805">
<![LOG[Expand a string: select * from Win32_ComputerSystem WHERE Manufacturer LIKE "%Dell%"]LOG]!><time="17:06:49.898-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="utility.cpp:805">
<![LOG[The condition for the group (Dell) is evaluated to be true]LOG]!><time="17:06:49.898-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="instruction.cxx:135">
<![LOG[The group (Dell) has been successfully started]LOG]!><time="17:06:49.898-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="instruction.cxx:156">
<![LOG[Set authenticator in transport]LOG]!><time="17:06:49.930-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="libsmsmessaging.cpp:7734">
<![LOG[Updated security on object C:\_SMSTaskSequence.]LOG]!><time="17:06:49.977-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="utils.cpp:1704">
<![LOG[Set a global environment variable _SMSTSNextInstructionPointer=7]LOG]!><time="17:06:49.977-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:668">
<![LOG[Set a TS execution environment variable _SMSTSNextInstructionPointer=7]LOG]!><time="17:06:49.977-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:386">
<![LOG[Set a global environment variable _SMSTSInstructionStackString=0 5 6]LOG]!><time="17:06:49.977-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:668">
<![LOG[Set a TS execution environment variable _SMSTSInstructionStackString=0 5 6]LOG]!><time="17:06:49.977-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:414">
<![LOG[Save the current environment block]LOG]!><time="17:06:49.977-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:833">
<![LOG[Start executing an instruction. Instruction name: Run PowerShell Script: COnfigure E5440 BIOS. Instruction pointer: 7]LOG]!><time="17:06:50.273-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="engine.cxx:116">
<![LOG[Set a global environment variable _SMSTSCurrentActionName=Run PowerShell Script: COnfigure E5440 BIOS]LOG]!><time="17:06:50.273-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:668">
<![LOG[Set a global environment variable _SMSTSNextInstructionPointer=7]LOG]!><time="17:06:50.273-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:668">
<![LOG[Set a local default variable OSDRunPowerShellScriptExecutionPolicy]LOG]!><time="17:06:50.273-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:700">
<![LOG[Set a local default variable OSDRunPowerShellScriptPackageID]LOG]!><time="17:06:50.273-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:700">
<![LOG[Set a local default variable OSDRunPowerShellScriptParameters]LOG]!><time="17:06:50.273-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:700">
<![LOG[Set a local default variable OSDRunPowerShellScriptScriptName]LOG]!><time="17:06:50.289-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:700">
<![LOG[Set a global environment variable _SMSTSLogPath=X:\WINDOWS\TEMP\SMSTSLog]LOG]!><time="17:06:50.289-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:668">
<![LOG[Evaluating an AND expression]LOG]!><time="17:06:50.289-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="tsexpreval.cpp:600">
<![LOG[Evaluating a WMI condition expression]LOG]!><time="17:06:50.289-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="tsexpreval.cpp:1879">
<![LOG[Expand a string: root\cimv2]LOG]!><time="17:06:50.289-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="utility.cpp:805">
<![LOG[Expand a string: select * from Win32_ComputerSystem
Where Model Like "%E5440%"]LOG]!><time="17:06:50.289-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="utility.cpp:805">
<![LOG[The condition for the action (Run PowerShell Script: COnfigure E5440 BIOS) is evaluated to be true]LOG]!><time="17:06:50.305-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="instruction.cxx:706">
<![LOG[Expand a string: OSDRunPowerShellScript.exe]LOG]!><time="17:06:50.305-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:782">
<![LOG[Expand a string: ]LOG]!><time="17:06:50.305-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:782">
<![LOG[Start executing the command line: OSDRunPowerShellScript.exe]LOG]!><time="17:06:50.305-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="instruction.cxx:722">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="17:06:50.305-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="instruction.cxx:751">
<![LOG[Expand a string: WinPEandFullOS]LOG]!><time="17:06:50.305-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:782">
<![LOG[Executing command line: OSDRunPowerShellScript.exe]LOG]!><time="17:06:50.305-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="commandline.cpp:827">
<![LOG[[ OSDRunPSScript.exe ]]LOG]!><time="17:06:50.336-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="main.cpp:312">
<![LOG[Running powershell script: 'configure-dellE5440_v3.ps1'(PkgID: S0100201) with execution policy: 'Bypass']LOG]!><time="17:06:50.336-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="main.cpp:342">
<![LOG[The execution scope for running the powershell script is specified not to verify the signature of the scripts. This is unsafe and potentially risk running malicious scripts.]LOG]!><time="17:06:50.336-180" date="10-21-2014" component="RunPowerShellScript" context="" type="2" thread="1952" file="main.cpp:345">
<![LOG[Sending warning status message]LOG]!><time="17:06:50.336-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="main.cpp:347">
<![LOG[Set authenticator in transport]LOG]!><time="17:06:50.336-180" date="10-21-2014" component="RunPowerShellScript" context="" type="0" thread="1952" file="libsmsmessaging.cpp:7734">
<![LOG[Powershell path: x:\Windows\System32\WindowsPowerShell\v1.0\]LOG]!><time="17:06:50.445-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="main.cpp:162">
<![LOG[ResolveSource flags: 0x00000000]LOG]!><time="17:06:50.445-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="resolvesource.cpp:3201">
<![LOG[SMSTSPersistContent: . The content for package S0100201 will be persisted]LOG]!><time="17:06:50.445-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="resolvesource.cpp:3212">
<![LOG[Locations: Multicast = 0, HTTP = 2, SMB = 0.]LOG]!><time="17:06:50.445-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="resolvesource.cpp:2749">
<![LOG[Multicast is not enabled for the package.]LOG]!><time="17:06:50.445-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="resolvesource.cpp:2789">
<![LOG[Trying http://DP1.fqdn.tld/SMS_DP_SMSPKG$/S0100201.]LOG]!><time="17:06:50.445-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="resolvesource.cpp:2870">
<![LOG[Set authenticator in transport]LOG]!><time="17:06:50.445-180" date="10-21-2014" component="RunPowerShellScript" context="" type="0" thread="1952" file="libsmsmessaging.cpp:7734">
<![LOG[WinHttp credentials set]LOG]!><time="17:06:50.445-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="downloadcontent.cpp:796">
<![LOG[List of files to be downloaded]LOG]!><time="17:07:12.800-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="downloadcontent.cpp:350">
<![LOG[Downloaded file from http://DP1.fqdn.tld:80/SMS_DP_SMSPKG$/S0100201/sccm?/backup/configure-delE5440.ps1 to C:\_SMSTaskSequence\Packages\S0100201\backup/configure-delE5440.ps1 ]LOG]!><time="17:07:54.868-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="downloadcontent.cpp:1592">
<![LOG[Executing command line: X:\WINDOWS\system32\cmd.exe /k]LOG]!><time="17:08:01.462-180" date="10-21-2014" component="TSBootShell" context="" type="1" thread="736" file="bootshell.cpp:860">
<![LOG[The command completed successfully.]LOG]!><time="17:08:01.462-180" date="10-21-2014" component="TSBootShell" context="" type="1" thread="736" file="bootshell.cpp:942">
<![LOG[Successfully launched command shell.]LOG]!><time="17:08:01.462-180" date="10-21-2014" component="TSBootShell" context="" type="1" thread="736" file="bootshell.cpp:432">
<![LOG[Downloaded file from http://DP1.fqdn.tld:80/SMS_DP_SMSPKG$/S0100201/sccm?/backup/configure-delE5440_v2.ps1 to C:\_SMSTaskSequence\Packages\S0100201\backup/configure-delE5440_v2.ps1 ]LOG]!><time="17:08:15.912-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="downloadcontent.cpp:1592">
<![LOG[Downloaded file from http://DP1.fqdn.tld:80/SMS_DP_SMSPKG$/S0100201/sccm?/cctkcmd.bat to C:\_SMSTaskSequence\Packages\S0100201\cctkcmd.bat ]LOG]!><time="17:08:15.912-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="downloadcontent.cpp:1592">
......<![LOG[Downloaded file from http://DP1.fqdn.tld:80/SMS_DP_SMSPKG$/S0100201/sccm?/X86_64/mxml1.dll to C:\_SMSTaskSequence\Packages\S0100201\X86_64/mxml1.dll ]LOG]!><time="17:29:20.557-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="downloadcontent.cpp:1592">
<![LOG[Downloaded file from http://DP1.fqdn.tld:80/SMS_DP_SMSPKG$/S0100201/sccm?/X86_64/pci.ids to C:\_SMSTaskSequence\Packages\S0100201\X86_64/pci.ids ]LOG]!><time="17:29:41.577-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="downloadcontent.cpp:1592">
<![LOG[Downloaded file from http://DP1.fqdn.tld:80/SMS_DP_SMSPKG$/S0100201/sccm?/X86_64/temp to C:\_SMSTaskSequence\Packages\S0100201\X86_64/temp ]LOG]!><time="17:29:41.593-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="downloadcontent.cpp:1592">
<![LOG[VerifyContentHash: Hash algorithm is 32780]LOG]!><time="17:29:41.608-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="downloadcontent.cpp:1870">
<![LOG[Resolved source to 'C:\_SMSTaskSequence\Packages\S0100201']LOG]!><time="17:29:42.327-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="main.cpp:216">
<![LOG[Working dir 'C:\_SMSTaskSequence\Packages\S0100201']LOG]!><time="17:29:42.327-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="main.cpp:237">
<![LOG[Executing command line: Run Powershell script]LOG]!><time="17:29:42.327-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="commandline.cpp:827">
<![LOG[Found cctk.exe from: C:\_SMSTaskSequence\Packages\S0100201\X86_64]LOG]!><time="17:29:54.968-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="main.cpp:29">
<![LOG[ocation: C:\_SMSTaskSequence\Packages\S0100201\X86_64, .\hapint64.exe ]LOG]!><time="17:29:54.968-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="main.cpp:29">
<![LOG[ttempt to install Dell HAPI ....]LOG]!><time="17:29:54.968-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="main.cpp:29">
<![LOG[Installation seems to be Ok...]LOG]!><time="17:30:00.112-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="main.cpp:29">
<![LOG[API installed.]LOG]!><time="17:30:00.112-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="main.cpp:29">
<![LOG[Found: Dell Command Configure Version 3.0.0 563 (Windows - Aug 20 2014, 16:38:09)]LOG]!><time="17:30:01.651-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="main.cpp:29">
<![LOG[Will log to X:\WINDOWS\TEMP\biossetup.log]LOG]!><time="17:30:01.651-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="main.cpp:29">
<![LOG[egin BIOS configuration ....]LOG]!><time="17:30:01.651-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="main.cpp:29">
<![LOG[onfiguration file: E5440.ini found.]LOG]!><time="17:30:01.651-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="main.cpp:29">
<![LOG[Bios Configuration Complete.]LOG]!><time="17:30:02.680-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="main.cpp:29">
<![LOG[ios password change: ...Changed]LOG]!><time="17:30:03.713-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="main.cpp:29">
<![LOG[rogram exit]LOG]!><time="17:30:03.713-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="main.cpp:29">
<![LOG[Process completed with exit code 0]LOG]!><time="17:30:04.088-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="commandline.cpp:1123">
<![LOG[Command line returned 0]LOG]!><time="17:30:04.088-180" date="10-21-2014" component="RunPowerShellScript" context="" type="1" thread="1952" file="main.cpp:258">
<![LOG[Process completed with exit code 0]LOG]!><time="17:30:04.088-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="commandline.cpp:1123">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="17:30:04.088-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="instruction.cxx:804">
<![LOG[Successfully completed the action (Run PowerShell Script: COnfigure E5440 BIOS) with the exit win32 code 0]LOG]!><time="17:30:04.104-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="instruction.cxx:830">
<![LOG[Set authenticator in transport]LOG]!><time="17:30:04.119-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="libsmsmessaging.cpp:7734">
<![LOG[Set a global environment variable _SMSTSLastActionRetCode=0]LOG]!><time="17:30:04.197-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:668">
<![LOG[Set a global environment variable _SMSTSLastActionSucceeded=true]LOG]!><time="17:30:04.197-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:668">
<![LOG[Expand a string: %_SMSTSMDataPath%\Logs]LOG]!><time="17:30:04.197-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:782">
<![LOG[Clear local default environment]LOG]!><time="17:30:04.213-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:807">
<![LOG[Updated security on object C:\_SMSTaskSequence.]LOG]!><time="17:30:04.213-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="utils.cpp:1704">
<![LOG[Set a global environment variable _SMSTSNextInstructionPointer=8]LOG]!><time="17:30:04.213-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:668">
<![LOG[Set a TS execution environment variable _SMSTSNextInstructionPointer=8]LOG]!><time="17:30:04.213-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:386">
<![LOG[Set a global environment variable _SMSTSInstructionStackString=0 5 6]LOG]!><time="17:30:04.229-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:668">
<![LOG[Set a TS execution environment variable _SMSTSInstructionStackString=0 5 6]LOG]!><time="17:30:04.229-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:414">
<![LOG[Save the current environment block]LOG]!><time="17:30:04.229-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:833">
<![LOG[Start executing an instruction. Instruction name: Dell. Instruction pointer: 8]LOG]!><time="17:30:04.525-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="engine.cxx:116">
<![LOG[Set a global environment variable _SMSTSCurrentActionName=Dell]LOG]!><time="17:30:04.525-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:668">
<![LOG[Set a global environment variable _SMSTSNextInstructionPointer=8]LOG]!><time="17:30:04.525-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:668">
<![LOG[The group (Dell) has been successfully completed]LOG]!><time="17:30:04.525-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="instruction.cxx:344">
<![LOG[Set authenticator in transport]LOG]!><time="17:30:04.557-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="libsmsmessaging.cpp:7734">
<![LOG[Updated security on object C:\_SMSTaskSequence.]LOG]!><time="17:30:04.604-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="utils.cpp:1704">
<![LOG[Set a global environment variable _SMSTSNextInstructionPointer=9]LOG]!><time="17:30:04.604-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:668">
<![LOG[Set a TS execution environment variable _SMSTSNextInstructionPointer=9]LOG]!><time="17:30:04.604-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:386">
<![LOG[Set a global environment variable _SMSTSInstructionStackString=0 5]LOG]!><time="17:30:04.604-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:668">
<![LOG[Set a TS execution environment variable _SMSTSInstructionStackString=0 5]LOG]!><time="17:30:04.604-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:414">
<![LOG[Save the current environment block]LOG]!><time="17:30:04.604-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:833">
<![LOG[Start executing an instruction. Instruction name: HP. Instruction pointer: 9]LOG]!><time="17:30:04.854-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="engine.cxx:116">
<![LOG[Set a global environment variable _SMSTSCurrentActionName=HP]LOG]!><time="17:30:04.870-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:668">
<![LOG[Set a global environment variable _SMSTSNextInstructionPointer=9]LOG]!><time="17:30:04.870-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:668">
<![LOG[Evaluating an AND expression]LOG]!><time="17:30:04.870-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="tsexpreval.cpp:600">
<![LOG[Evaluating a WMI condition expression]LOG]!><time="17:30:04.870-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="tsexpreval.cpp:1879">
<![LOG[Expand a string: root\cimv2]LOG]!><time="17:30:04.870-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="utility.cpp:805">
<![LOG[Expand a string: select * from Win32_ComputerSystem WHERE Manufacturer LIKE "%Hewlett-Packard%"]LOG]!><time="17:30:04.870-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="utility.cpp:805">
<![LOG[The group (HP) has been skipped because the condition is evaluated to be false]LOG]!><time="17:30:04.885-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="instruction.cxx:118">
<![LOG[Set authenticator in transport]LOG]!><time="17:30:04.916-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="libsmsmessaging.cpp:7734">
<![LOG[Execution of the instruction (HP) has been skipped]LOG]!><time="17:30:04.963-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="engine.cxx:192">
<![LOG[Start executing an instruction. Instruction name: Restart Computer. Instruction pointer: 12]LOG]!><time="17:30:04.963-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="engine.cxx:116">
<![LOG[Set a global environment variable _SMSTSCurrentActionName=Restart Computer]LOG]!><time="17:30:04.979-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:668">
<![LOG[Set a global environment variable _SMSTSNextInstructionPointer=12]LOG]!><time="17:30:04.979-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:668">
<![LOG[Set a local default variable SMSRebootMessage]LOG]!><time="17:30:04.979-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:700">
<![LOG[Set a local default variable SMSRebootTimeout]LOG]!><time="17:30:04.979-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:700">
<![LOG[Set a global environment variable _SMSTSLogPath=X:\WINDOWS\TEMP\SMSTSLog]LOG]!><time="17:30:04.979-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:668">
<![LOG[Expand a string: smsboot.exe /target:WinPE]LOG]!><time="17:30:04.979-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:782">
<![LOG[Expand a string: ]LOG]!><time="17:30:04.979-180" date="10-21-2014" component="TSManager" context="" type="0" thread="1564" file="executionenv.cxx:782">
<![LOG[Start executing the command line: smsboot.exe /target:WinPE]LOG]!><time="17:30:04.979-180" date="10-21-2014" component="TSManager" context="" type="1" thread="1564" file="instruction.cxx:722">
Donloading about 16 Mb package takes about 25...30 minutes.
Drivers for this model: 750mb, 1 - 1½ hours.
11 applications (in 2 phases, depending manufacturer/model), less than 5 mb, ¨~ 500 Mb.
~T

System role change in Sol Man

Dear friends,
I am working with Solution Manger 4.0. In Solar01, in top menu option, under "Business Blueprint", we are having option to change the "System role".
I wants to restrict this option based on the user ID. Because, now everybody logins to different systems (means DEV,QA,PRD) by changing the system role.
How to restrict this option?
Thanks
Senthil

Hello Sentil,
The functionality you are looking for is not available.
However, you may consider the following to achieve a similar result:
In SOLAR_PROJECT_ADMIN of the respective project, tab System Landscape, sub tab Systems there is a button calls System Landscape Assignment via which you can project specifically hide certain system roles. So for instance if during business blueprinting you only need the evaluation and development systems, you can hide the system roles which are not required at that point of time, such as QA and PRD. The result: Project team members working on SOLAR01 and SOLAR02 for instance can only see the roles which have been defined in SOLAR_PROJECT_ADMIN.
At a later project stage you can then add QA and PRD if required simply by adding the respective system roles again. The information on system-clients assigned is simply retrieved from the system landscape maintenance (SMSY transaction), where this information still resides.
So this might be an alternative to your suggestion (system roles based on user ID) because in this way you have control of offering system roles and, thus, the respective systems project-phase-dependently.
Best regards,
Doreen

H:messages - Display order

Hi,
I have a form where the user enters *(1.zipcode 2.phone number 3.email address)* and i am using h:messages to display the messages at the top of the page. I would like the error messages to be displayed in the order of input field validations. JSF1.2 is displaying error messages in random order.
Scenario:+
User leaves all the fields blank and clicks submit.
Error messages are displayed in some order by JSF1.2:
Please enter email address.
Please enter phone number.
Please enter zipcode.
I want them to be displayed in this order:
Please enter zipcode.
Please enter phone number.
Please enter email address.
Is there a way i can specify to JSF to display the error messages in the order of input field validations?
Appreciate your help.
Thanks
vamsi

The standard messages component will output the messages in the order they are queued by the code. Do you have something unusual happening that would change the order of the component validation?
In any case, some potential solutions:
1) Use <h:message> with the for attribute and place the messages in the order you desire.
2) Create a custom messages component, which provides a sorting interface.
3) Use a PhaseListener to rebuild the message queue in the correct order before the Render Response phase (depends on the Iterators returned from FacesContext.getMessages() being modifiable).

Audio encoding troubles

After some time off, I'm again burning old family vhs and Hi8 tapes to dvd but this time w/our new intel core duo. I've tried varying the themes in iDVD but with some of them I get the spinning beach ball after the video encoding--at the beginning of the audio encoding. It simpy hangs up after about 30 seconds and the dreaded beach ball appears. I've tried to re-burn after splitting the clips so that none are longer than 15 minutes--still no go. I never add music so the only audio is from the original tapes or the default music with associated with the theme. This was never a problem with the dvds I creaed on our G4 using some of the older iDVD themes. Any ideas? thanks

This was never a problem with the dvds I creaed on
our G4 using some of the older iDVD themes.
This lack of positive feedback has been around since
version 5 and has nothing to do with themes. Just
"bad" feedback.
http://docs.info.apple.com/article.html?artnum=302988
My computer can take up to 30 minutes to get through
this phase, depending on the iDVD project. Takes even
longer for some people; like overnight...
What I've done a few times is "force quit" and start over at the "share iMovie with iDVD" stage. Sometimes, after re-creating the iDVD project with the same Theme settings it whips right through the audio encoding (although it also has had to redo the video encoding first). I get frantic whenever I see the beachball on the screen and my impulse it to force quit whatever application I'm in.

Prepare_clone.pl script has nothing in it

I am trying to clone an ORACLE_HOME.
According to Oracle documentation, to prepare the ORACLE_HOME at the source, I need to run prepare_clone.pl. I ran it and it exited immediately with no errors.
I happened to look at the contents of the perl script. There is nothing in it!
Just an "exit 0;" statement. Is this right? Oracle claims this script does a bunch of things to prepare the ORACLE_HOME for cloning.
thanks
Boris

I noticed the documentation also says:
"Note:
The need to perform the preparation phase depends on the Oracle product that you are installing. This script needs to be executed only for the Application Server Cloning. Database and CRS Oracle home Cloning does not need this."
I don't have an Application Server installation so I don't know if that file contains anything if it's part of an Application Server or not. In the database I work with, that file is also empty except for "exit 0".
Tom

Appraisal Element Access based on Rows

Hi All,
We are using SAP ECC 6 HR patch level 18, where we are implementing performance appraisal (objectives based).
The control of Appraisal elements(display, change, hide) is based on the columns. Currently we have created columns for each individual role (1 appraisee + 3 appraiser roles) for 2 appraisal review periods within a year resulting to 8 columns and lot of horizontal scrolling in the form, which in portal is very cumbersome. We are using BSP pages in the portal.
We thought of reducing the number of columns by combining the appraiser's columns. But with this the column access control will not work, as each of the appraiser can access other appraiser columns.
Is there a way to control elements based on the row, so that different appraisers can have different rows at different statuses and substatuses.
Regards,
Vijay Warrier

Hi,
You can set the column access as per the requiremnt.
1. Set the column owner for the column first.
2. Then set the rights the owner and others have to be set for each phase (Planning, Review and Part-appraisal and final appraisal) .
Typically the column owner will have all the rights. Other's rights will depend on the appraisal process.
3. Do this for all the columns available for your template.
4. This would come under the phase dependent acces type.
5. Also criteria level settings can be done for each criteria from ECC 5.0 onwards depending on the role of the participant.
Hope this helps you.
Regards,
Subbu

Phase Dependency in DAC

Similar Messages

Maybe you are looking for